Microsoft has announced their intention to enable plus addressing across Exchange Online in January 2022. Plus addressing is a good capability, but it might cause some problems for tenants with mail-enabled recipients that have plus addresses in their set of proxy email addresses. Fortunately, we've written some PowerShell code to report those pesky addresses and to remove them if you want to do a big clean up before Microsoft makes the big switch in five months' time.
It's a good idea to replace older calls to the Get-Mailbox cmdlet with Get-ExoMailbox. However, it's not just a matter of cut and paste updates. In some cases, the nature of the new REST-based cmdlets mean that some additional care is necessary to ensure that the updated code works as expected. As we examine in this article, filters are just one example where some attention to detail is needed to make sure Exchange Online delivers the right set of mailbox data.
An earlier article explained how to create organizational contacts in user mailboxes with Graph API calls. This article builds on that idea with three improvements. First, we select target mailboxes for update by looking for those added in the last month. Second, we allow any mail-enabled recipient to be added as an organizational contact. Third, we incorporate some code to check if a contact already exists in a mailbox. Like anything with PowerShell, this code can be improved..
It's important to know if a tenant has any very large distribution lists as these might be the source of reply-all mail storms. An old article explains how to report the membership counts for distribution lists on an on-premises Exchange server. Life is different in the cloud, and we need to take a different approach. This article explains how to use different calls in a PowerShell script to create a nice report about distribution list memberships.
A variety of methods exist to block access to a user's Office 365 (Azure AD) account from a complete block to a conditional access policy. In this article, we examine the various methods and debate the worth of each approach. Conditional access policies are the cleanest and most effective long-term solution, but you need Azure AD premium licenses. If you don't have those licenses, maybe one of the other approaches will work for you.
The New-DistributionGroup cmdlet has been in Exchange since 2006. It creates a new distribution list that is easily populated with a few commands. Although Microsoft might like everyone to use the new-fangled Microsoft 365 Groups, the fact remains that distribution lists are very useful. So much so that many millions are still in active use. In this article, we explore how to create new standard and dynamic distribution lists with PowerShell.
Sensitivity labels are an effective way to manage containers like Teams, Microsoft 365 Groups, and SharePoint sites. Microsoft doesn't provide any way to track changes made to labels assigned to containers, which means that a group owner can downgrade the policy assigned through a label. This article explains a method to detect when label changes occur for containers and how to revert those changes if necessary.
Many apps are created in the Azure AD for a tenant. Those apps have permissions to allow them to access data, and consent for those permissions are granted by administrators and users. How often do you check what apps are known in your Azure AD and what permissions those apps have? In this article, we review how to use the Graph API and PowerShell to create a report inventorying apps and permissions. What you do with that data is up to you!
Microsoft provides many methods to manage a tenant’s data and users. PowerShell is a powerful tool to manage resources, including Conditional Access Policies using a set of cmdlets in the AzureAD module. In this article, Microsoft MVP Damian Scoles reviews the eight PowerShell cmdlets and how to use them.
In this how-to guide, Daler Sayfiddinov demonstrates how to use PowerShell to migrate data from a CSV file to SharePoint.