
There are a couple of different ways to create a dynamic DL. The owner of the dynamic DL does not need to be IT or have any elevated roles in the tenant. I’ve also had customers set one of these up and send News Digests from SharePoint Online to it. Dynamic DLs cannot be upgraded to Office 365 Groups. If you currently have any static DLs they cannot be changed to dynamic DLs, but they can be upgraded to Office 365 Groups. If there’s no rule, emails sent to that DL end up in every mailbox in your tenant. In the case of a dynamic DL the way to get everyone is to create no rule. When you create a dynamic anything you have to provide a rule so that Azure AD (AAD) knows whether someone should be in the thing or not. To do this, create a new DL and make it a dynamic DL. Get here quick before Gary eats them all” or “The CEO is feeling generous and she’s giving everyone (except Gary) Friday off!” DLs are email only and they’re a good way to send out company wide things like “There are donuts in the breakroom. These things have been around since shortly after prehistoric fish came on land from the primordial soup and they’ve been going strong ever since. The first option I’ll cover is the old tried and true email Distribution List.
#HOW TO SYNC OFFICE 365 GROUPS WITH AD WINDOWS#
All of these examples also assume the groups are cloud only, not synced from on-prem Windows Active Directory.
#HOW TO SYNC OFFICE 365 GROUPS WITH AD HOW TO#
All of my examples will show how to keep the All User list populated automatically. Your company could already handle adding people to Distribution Lists (DLs) as part of your onboarding process. They all leverage the functionality of updating dynamically as people join your company. There are several “All User” communication methods that have come up in my discussions with customers.

I’ll leave the why up to people that are smarter than me. I won’t cover why you should employ any of these techniques, but how you can do them if you have already decided they are a good idea. This post is meant to be technical, not prescriptive. But every time a customer asks me about it I understand it a little better, so I threw this blog post together to point people at if they want to do it. I’m usually not a fan of big blast communication like that, and in the case of products that are built on top of Microsoft 365 Groups, there are published limitations to this. What’s the topic? It boils down to, “How do I create a Team/Distribution List/SharePoint site that is always available everyone in the company?” The first couple of times the topic came up I tried to talk the customer out of it. It just keeps coming up, I’m guessing because the adoption of Office 365 has really taken off in the last 5 months. I swear I’ve had this conversation half a dozen times in last month after having never had it at all before. Some blog posts just beg to be written, and this is one of them.
