Microsoft Docs - Latest Articles

As the new home for Microsoft technical documentation, docs.microsoft.com has not only modernized the web experience for content, but also how we create and support the content you use to learn, manage and deploy solutions. It is the one-stop shop for everything related to Microsoft technologies. In order to make sure you can keep up to date on what’s new and exciting on docs.microsoft.com, we’ve created a dedicated feed for you.


Selected Feed: Microsoft 365

Windows Microsoft Azure Visual Studio Office Microsoft 365 .Net ASP.NET Sql Enterprise Mobility Security Nuget Dynamics 365 Xamarin Azure DevOps System Center Powershell

New-Team (MicrosoftTeamsPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/teams/new-team 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.
Published Date : Wednesday, September 16, 2020

Set-PnPTenant (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/set-pnptenant 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.
Published Date : Tuesday, November 28, 2017

Set-PnPMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/set-pnpmicrosoft365group Required Permissions Microsoft Graph API: Group.ReadWrite.All Sets Microsoft 365 Group properties
Published Date : Tuesday, November 28, 2017

Restore-PnPDeletedMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/restore-pnpdeletedmicrosoft365group Required Permissions Microsoft Graph API: Group.ReadWrite.All Restores one deleted Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Reset-PnPMicrosoft365GroupExpiration (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/reset-pnpmicrosoft365groupexpiration Renews the Microsoft 365 Group by extending its expiration with the number of days defined in the group expiration policy set on the Azure Active Directory
Published Date : Tuesday, November 28, 2017

Remove-PnPMicrosoft365GroupOwner (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/remove-pnpmicrosoft365groupowner Required Permissions Microsoft Graph API : One of Directory.ReadWrite.All, Group.ReadWrite.All Removes owners from a particular Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Remove-PnPMicrosoft365GroupMember (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/remove-pnpmicrosoft365groupmember Required Permissions Microsoft Graph API : One of Directory.ReadWrite.All, Group.ReadWrite.All, GroupMember.ReadWrite.All Removes members from a particular Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Remove-PnPMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/remove-pnpmicrosoft365group Required Permissions Microsoft Graph API: Group.ReadWrite.All Removes one Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Remove-PnPDeletedMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/remove-pnpdeletedmicrosoft365group Required Permissions Microsoft Graph API: Group.ReadWrite.All Permanently removes one deleted Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

New-PnPMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnpmicrosoft365group Required Permissions Microsoft Graph API : One of Directory.ReadWrite.All, Group.Create, Group.ReadWrite.All Creates a new Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

New-PnPTenantSequenceTeamNoGroupSubSite (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnptenantsequenceteamnogroupsubsite Creates a team site subsite with no Microsoft 365 group object
Published Date : Tuesday, November 28, 2017

New-PnPSite (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnpsite The New-PnPSite cmdlet creates a new site collection for the current tenant. Currently only 'modern' sites like Communication Site and the Modern Microsoft 365 group-connected team sites are supported. If you want to create a classic site, use New-PnPTenantSite.
Published Date : Tuesday, November 28, 2017

New-PnPTeamsTeam (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnpteamsteam Required Permissions Microsoft Graph API: Group.ReadWrite.All Creates a new Team in Microsoft Teams. The cmdlet will create a Microsoft 365 group and then add a team to the group.
Published Date : Tuesday, November 28, 2017

New-PnPTenantSequenceTeamNoGroupSite (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnptenantsequenceteamnogroupsite Creates a new team site without a Microsoft 365 group in-memory object
Published Date : Tuesday, November 28, 2017

Get-PnPMicrosoft365GroupMembers (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpmicrosoft365groupmembers Required Permissions Microsoft Graph API : One of Directory.Read.All, Directory.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, GroupMember.Read.All, GroupMember.ReadWrite.All, User.Read.All, User.ReadWrite.All Gets members of a particular Microsoft 365 Group (aka Unified Group). Requires the Azure Active Directory application permissions 'Group.Read.All' and 'User.Read.All'.
Published Date : Tuesday, November 28, 2017

Get-PnPMicrosoft365GroupOwners (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpmicrosoft365groupowners Required Permissions Microsoft Graph API : One of Group.Read.All, Group.ReadWrite.All, User.Read.All, User.ReadWrite.All Gets owners of a particular Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Get-PnPMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpmicrosoft365group Required Permissions Microsoft Graph API : One of Directory.Read.All, Directory.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, GroupMember.Read.All, GroupMember.ReadWrite.All Gets one Microsoft 365 Group or a list of Microsoft 365 Groups
Published Date : Tuesday, November 28, 2017

Get-PnPDeletedMicrosoft365Group (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpdeletedmicrosoft365group Required Permissions Microsoft Graph API : One of Group.Read.All, Group.ReadWrite.All Gets one deleted Microsoft 365 Group or a list of deleted Microsoft 365 Groups
Published Date : Tuesday, November 28, 2017

Add-PnPMicrosoft365GroupMember (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpmicrosoft365groupmember Required Permissions Microsoft Graph API: All of Group.ReadWrite.All, User.ReadWrite.All Adds members to a particular Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Clear-PnPMicrosoft365GroupMember (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/clear-pnpmicrosoft365groupmember Required Permissions Microsoft Graph API : One of Directory.ReadWrite.All, Group.ReadWrite.All, GroupMember.ReadWrite.All Removes all current members from a particular Microsoft 365 Group
Published Date : Tuesday, November 28, 2017

Add-PnPTeamsTeam (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpteamsteam This command allows you to add a Teams team to an existing, Microsoft 365 group connected, site collection.
Published Date : Tuesday, November 28, 2017

Add-PnPMicrosoft365GroupToSite (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpmicrosoft365grouptosite This command allows you to add a Microsoft 365 Unified group to an existing classic site collection, also known as groupifying.
Published Date : Tuesday, November 28, 2017

Clear-PnPMicrosoft365GroupOwner (SharePointPnPPowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/clear-pnpmicrosoft365groupowner Required Permissions Microsoft Graph API : One of Directory.ReadWrite.All, Group.ReadWrite.All Removes all current owners from a particular Microsoft 365 Group (aka Unified Group)
Published Date : Tuesday, November 28, 2017

Set-SPOSiteOffice365Group (SharePointOnlinePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/set-spositeoffice365group Connects a top-level SPO site collection to a new Microsoft 365 Group. You must be a SharePoint Online administrator or 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.
Published Date : Tuesday, November 28, 2017

Set-SPOSite (SharePointOnlinePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/set-sposite 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 administrator or Global Administrator and be 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.
Published Date : Tuesday, November 28, 2017

Add-SPOGeoAdministrator (SharePointOnlinePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/add-spogeoadministrator This cmdlet requires a connection to a multi-geo tenant to run correctly. You must be a SharePoint Online administrator or Global Administrator to run this cmdlet.
Published Date : Tuesday, November 28, 2017

Get-SPOSite (SharePointOnlinePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/get-sposite 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 administrator or Global Administrator and be 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. 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.
Published Date : Tuesday, November 28, 2017

SharePoint PowerShell

 https://docs.microsoft.com/en-us/powershell/sharepoint/ Use PowerShell cmdlets for SharePoint in Microsoft 365 and SharePoint Server
Published Date : Monday, March 16, 2020

Validate-OutboundConnector (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/validate-outboundconnector 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.
Published Date : Monday, September 25, 2017

Upgrade-DistributionGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/upgrade-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.
Published Date : Monday, September 25, 2017

Update-HybridConfiguration (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/update-hybridconfiguration You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Undo-SoftDeletedUnifiedGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/undo-softdeletedunifiedgroup 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-AzureADMSDeletedGroup cmdlet in Azure Active Directory PowerShell. To permanently remove (purge) a soft-deleted Microsoft 365 Group, use the Remove-AzureADMSDeletedDirectoryObject cmdlet in Azure Active Directory PowerShell. For more information, see Permanently delete a Microsoft 365 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.
Published Date : Monday, September 25, 2017

Test-MigrationServerAvailability (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/test-migrationserveravailability The Test-MigrationServerAvailability cmdlet verifies that you can communicate with the on-premises mail server that houses the mailbox data that you want to migrate to cloud-based mailboxes. When you run this cmdlet, you must specify the migration type. You can specify whether to communicate with an IMAP server or with an Exchange server. For an IMAP migration, this cmdlet uses the server's fully qualified domain name (FQDN) and a port number to verify the connection. If the verification is successful, use the same connection settings when you create a migration request with the New-MigrationBatch cmdlet. 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.
Published Date : Monday, September 25, 2017

Test-OAuthConnectivity (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/test-oauthconnectivity 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. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Stop-MigrationBatch (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/stop-migrationbatch 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.
Published Date : Monday, September 25, 2017

Set-UserPhoto (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-userphoto 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.
Published Date : Monday, September 25, 2017

Set-TransportRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-transportrule In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role. 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.
Published Date : Monday, September 25, 2017

Set-User (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-user 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.
Published Date : Monday, September 25, 2017

Set-UnifiedGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup Microsoft 365 Groups are group objects that are available across Microsoft 365 services. The HiddenGroupMembershipEnabled parameter is only available on the New-UnifiedGroup cmdlet. You can't change this setting on an existing Microsoft 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.
Published Date : Monday, September 25, 2017

Set-UnifiedAuditLogRetentionPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-unifiedauditlogretentionpolicy 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. You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-TransportConfig (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-transportconfig You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-SiteMailboxProvisioningPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-sitemailboxprovisioningpolicy 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.
Published Date : Monday, September 25, 2017

Set-SendConnector (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-sendconnector You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-RetentionCompliancePolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-retentioncompliancepolicy You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-ProtectionAlert (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-protectionalert You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-OwaMailboxPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-owamailboxpolicy 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 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.
Published Date : Monday, September 25, 2017

Set-OutboundConnector (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-outboundconnector 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.
Published Date : Monday, September 25, 2017

Set-OrganizationConfig (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-organizationconfig You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-OnPremisesOrganization (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-onpremisesorganization 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.
Published Date : Monday, September 25, 2017

Set-OMEConfiguration (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-omeconfiguration You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-OMEMessageRevocation (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-omemessagerevocation 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.
Published Date : Monday, September 25, 2017

Set-Mailbox (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-mailbox 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.
Published Date : Monday, September 25, 2017

Set-LabelPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-labelpolicy You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-InboundConnector (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboundconnector 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.
Published Date : Monday, September 25, 2017

Set-IRMConfiguration (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-irmconfiguration 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.
Published Date : Monday, September 25, 2017

Set-HybridConfiguration (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-hybridconfiguration 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.
Published Date : Monday, September 25, 2017

Set-FederationTrust (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-federationtrust 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.
Published Date : Monday, September 25, 2017

Set-EmailAddressPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-emailaddresspolicy 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.
Published Date : Monday, September 25, 2017

Set-DeviceConditionalAccessRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-deviceconditionalaccessrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DistributionGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-distributiongroup 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.
Published Date : Monday, September 25, 2017

Set-DeviceConfigurationPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-deviceconfigurationpolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DeviceTenantPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-devicetenantpolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DlpCompliancePolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-dlpcompliancepolicy You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DeviceTenantRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-devicetenantrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DeviceConfigurationRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-deviceconfigurationrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-DeviceConditionalAccessPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-deviceconditionalaccesspolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-ComplianceSecurityFilter (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-compliancesecurityfilter You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-ComplianceSearch (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-compliancesearch You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet. 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-AtpPolicyForO365 (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-atppolicyforo365 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. 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 ATP for SharePoint, OneDrive, and Microsoft Teams. You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-AutoSensitivityLabelPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-autosensitivitylabelpolicy You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-App (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-app The Set-App cmdlet can only be used when configuring the availability of an organization app. This task 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 Outlook). 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 and Manage deployment of add-ins in the Microsoft 365 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.
Published Date : Monday, September 25, 2017

Set-AntiPhishPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-antiphishpolicy You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Set-AdminAuditLogConfig (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-adminauditlogconfig When audit logging is enabled, a log entry is created for each cmdlet run, excluding Get cmdlets. Log entries are stored in a hidden mailbox and accessed using the Search-AdminAuditLog or New-AdminAuditLogSearch cmdlets. The Set-AdminAuditLogConfig, Enable-CmdletExtensionAgent, and Disable-CmdletExtensionAgent cmdlets are logged when they're run regardless of whether administrator audit logging is enabled or disabled. Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make may not be immediately applied to all Exchange servers in your organization. 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.
Published Date : Monday, September 25, 2017

Set-AuditConfig (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-auditconfig You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-ActivityAlert (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-activityalert You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Set-AccessToCustomerDataRequest (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/set-accesstocustomerdatarequest You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Search-UnifiedAuditLog (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/search-unifiedauditlog 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 Security & Compliance Center. For more information, see Audited 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. This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any 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.
Published Date : Monday, September 25, 2017

Search-MailboxAuditLog (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/search-mailboxauditlog 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. This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any 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.
Published Date : Monday, September 25, 2017

Rotate-DkimSigningConfig (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/rotate-dkimsigningconfig You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Remove-UserPhoto (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-userphoto 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.
Published Date : Monday, September 25, 2017

Remove-UnifiedGroupLinks (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-unifiedgrouplinks 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.
Published Date : Monday, September 25, 2017

Remove-UnifiedGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-unifiedgroup 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.
Published Date : Monday, September 25, 2017

Remove-OMEConfiguration (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-omeconfiguration You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Remove-OnPremisesOrganization (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-onpremisesorganization 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.
Published Date : Monday, September 25, 2017

Remove-EmailAddressPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-emailaddresspolicy You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

Remove-DeviceTenantRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-devicetenantrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-DeviceConditionalAccessRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-deviceconditionalaccessrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-DeviceConditionalAccessPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-deviceconditionalaccesspolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-DeviceConfigurationPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-deviceconfigurationpolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-DeviceTenantPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-devicetenantpolicy 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-DeviceConfigurationRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-deviceconfigurationrule 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 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 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-ComplianceCase (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-compliancecase You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

Remove-BlockedSenderAddress (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/remove-blockedsenderaddress You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

New-UnifiedGroup (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-unifiedgroup 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.
Published Date : Monday, September 25, 2017

New-UnifiedAuditLogRetentionPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-unifiedauditlogretentionpolicy 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. You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

New-TransportRule (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-transportrule In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role. 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.
Published Date : Monday, September 25, 2017

New-SendConnector (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-sendconnector You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
Published Date : Monday, September 25, 2017

New-SiteMailboxProvisioningPolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-sitemailboxprovisioningpolicy 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.
Published Date : Monday, September 25, 2017

New-ProtectionAlert (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-protectionalert You need to be assigned permissions in the Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017

New-RetentionCompliancePolicy (ExchangePowerShell)

 https://docs.microsoft.com/en-us/powershell/module/exchange/new-retentioncompliancepolicy 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 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in the Security & Compliance Center.
Published Date : Monday, September 25, 2017