Recent Discussions
Tenant-to-Tenant Migration with Orchestrator – Technical Overview (Microsoft 365 | Preview)
Tenant-to-tenant migration with Orchestrator in Microsoft 365 introduces a native, API-driven, and highly validated approach for cross-tenant migrations. It is designed for enterprise scenarios where sequencing, dependencies, and governance are critical. Note: This capability is currently in preview. Features and behavior may change before GA. Architecture and execution model Migration is executed through batches (jobs) managed via Microsoft Graph (Beta) User-level execution: one user failing validation does not block others in the same batch Mandatory Standalone Validation before migration submission Date-driven cutover using completeAfterDateTime Supported workloads (actual scope) Exchange Online Microsoft Teams ODSP (OneDrive for Business) Important clarification on SharePoint Orchestrator does not migrate shared SharePoint content such as Team sites, Channel sites, or collaboration sites. The ODSP workload covers personal user data (OneDrive) only. SharePoint team/workload sites remain out of scope and require separate tooling or processes. Critical prerequisites Identity Mapping (CTIM) is mandatory and must remain stable during migration Target users must not have Exchange mailboxes or OneDrive sites provisioned before migration Licenses must be assigned only after Identity Mapping (ExchangeGuid stamping) Migration apps and service principals (Teams, Meetings, CTMS) must be correctly provisioned Organization Relationships and Migration Endpoints must be in place Exchange autoforwarding must be enabled for Meetings migration Validation and lifecycle Standalone Validation acts as a full “what-if” check Key states include: Cancellation or user removal is possible only before cutover Post-migration cleanup After completion, tenants must be returned to a non-migration state: Remove Identity Mapping data Remove Organization Relationships Remove Migration Endpoints Revoke migration app permissions and service principals Decide whether to retain or remove MailUsers in the source tenant Skipping cleanup leaves the tenant in an exception state. When this approach fits Mergers and acquisitions Divestitures and tenant splits Regulated environments requiring strict control Scenarios where dependency-aware sequencing matters more than speed Technical conclusion Orchestrator is not a one-click solution. It delivers native orchestration, deep validation, and predictable execution when Identity Mapping, licensing order, and scope boundaries are fully understood. For experienced administrators and architects, it represents a major step forward in tenant-to-tenant migrations within Microsoft 365, even while still in preview.New Group Members not seeing Appointments
We are trying to determine why members that recently have joined a group do not see meetings that were scheduled before they joined, but are set for future dates. The one particular instance I'm chasing is a recurring meeting that was created before I joined the group. The person who created the invite has also updated the meeting details, should this not kick off some trigger to new groupies? Office 365 support has indicated that this is expected behavior. Would like to get a firm answer.
Unable to change primary SMTP of a group
I have a 365 group linked to Teams, with the primary SMTP address of mailto:HumanResources@(domain) I have been trying to change that by promoting an alias (PTmailto:onTeams@(domain)) to be the new primary. Every time I do this, it reverts to the original HumanResources address. A bit of searching suggested I try checking the primary address with the Get-UnifiedGroup powershell command, then setting it with Set-UnifiedGroup. Unfortunately, Get-UnifiedGroup shows that the primary SMTP is the desired PTonTeams address. It just isn't showing as such on the Exchange admin page. If I look up that same group in Azure, it also shows that it has the original address set as Primary SMTP. Can anyone shed some light on what might be going on and help me change this email address? Thank you!
Help Shape the Future of Groups and Copilot in M365
M365 Groups team is exploring two key areas to improve and simplify collaboration through Groups and Copilot. Your feedback will help us understand how you use Copilot with M365 Groups and Teams Channels today and identify opportunities to simplify and modernise group types. Copilot with Groups and Teams Channels Knowledge - We want to understand how you use Copilot today and how you leverage them for M365 Groups and Teams Channels Knowledge. Tell us your top scenarios, challenges, and what would make Copilot more valuable. Groups Usage and Simplification - Using and managing multiple groups types like M365 Groups, Security Groups, Mail Enabled Security Groups, Distribution Groups can be complex. We want to understand your current usage, pain points, and ideas for simplifying this. Please take a few minutes to share your insights through this survey - https://forms.office.com/r/CJLuuzEYQg
I upgraded a DL to a 365 Group. Can I create and link a SharePoint site?
As above, I upgraded one of our existing Distribution Lists to a Microsoft 365 group. Everything appears to have worked correctly, but there's no SharePoint site that would be created automatically when creating a group from scratch. Is there a way to create a new SharePoint site and link it to the existing group? I know I could make a classic site then link it to a New group, essentially I want to do that but link it to the newly created group.
'Sender Restrictions' for Office 365 Groups
In our company, as part of our move from Exchange on-prem to Exchange Online, we are considering replacing our current Exchange Distribution Lists with Dynamic Office 365 Groups. Many of these top-level Exchange Distribution Lists have Sender Restrictions imposed in order to limit who can send an email to the DL membership. For example, only certain users can send an email to a Distribution List that contains several thousand staff. We are unsure as to whether Dynamic Office 365 Groups can provide similar functionality. From what I have read, any members of a Dynamic Office 365 Group have the ability to send an email to the entire group membership. There does not appear to be any way to limit this ability. Is this correct ?
Dynamic Membership Added Users Receive "Access Denied" accessing SharePoint Site
Greetings everyone. Before I created this post, I did browse the internet and these forums for a possible solution. Of the items I found, they all stated permissions eventually propagated to the affected users. Here's the situation. I created several 365 groups for departments. I used dynamic membership to add users based on their department attribute. This was done back at the end of September. I'm receiving reports of users unable to access their department site. When I check either Azure AD, 365 Admin Center, or the 365 site, members show. Upon checking permissions on their SharePoint site, however; I find all users except Owners can access the site. Everyone else has None for permission level. We have done this setup for other departments, but this is the first one we've ever seen do this. All members exist in the group as I can use it for other permissions elsewhere in our tenancy. Has anyone seen something like this before? I'm wondering if turning the group back to Assigned from Dynamic, waiting an hour for all members to be removed, then setting it back to Dynamic with the rule. It seems strange that the permissions have not propagated after all this time.Group SP Site (Group image/logo Not Updating)
We have several groups we are working with, all have had a group image applied, but the Group Image doesnt seem to propogate to the connected SharePoint site (just get the colored background with two letters). Should the image populate automatically, or is this the expected behavior and SharePoint Site logos have to be manually set?Tenant gelöscht, kein Admin Center, wie Produktkauf widerrufen?
Hallo zusammen, ich hatte bis gestern zwei o365 Lizenzen "Business Essential" über einen Reseller mit eigener Domain. Das wurde mir zu teuer und ich habe am letzten Tag der Gültigkeit über den Admin Account direkt bei MS zwei Lizenzen gekauft "Exchange Online (Plan 1)" und den beiden Accounts zugwiesen. Leider hat der Reseller gestern dann alles gelöscht, sodass ich keinen Zugriff mehr auf irgendwas habe. Nun versuche ich, den Kauf bei MS zu widerrufen aber niemand bei MS fühlt sich so richtig zuständig. Mail an mailto:email address removed for privacy reasons sagt ich sollte über das Admin Center Kontakt aufnehmen 'email address removed for privacy reasons' mit Formular im Anhang sagt, ich sollte über das Admin Center Kontakt aufnehmen. Ich habe keine Lust, mir einen neuen Business Account zuzulegen und nochmal keine Kreditkartendaten zu hinterlegen. Die Hotline-Stimme kann mir auch nicht helfen, weil meine bis vorgestern mit MS verknüpfte Domain nicht mehr verknüpft ist und kein Account gefunden kann (haha). So langsam bin ich am verzweifeln... Noch eine Idee vielleicht? Beste Grüße Olli365 Groups - No "From" Dynamic Field
My organization is transitioning from shared mailboxes to Groups sometime in the near future and I updating my flows. I see there is no "From" field included for the trigger "When an email arrives to a group". What are we supposed to do in lieu of that if we need that trigger field?How to hard delete on a private channel within 30 days of deletion
Hi, my team uses private channels in our data team to share private data with other members of our org. We found out we are capped at 30 private channels, so we deleted some private channels then realized Microsoft only does a 'soft delete' for 30 days in order to allow one to restore the channel is needed. This would be fine, but the deleted channels still count towards the 30 channel max for 30 days. Is there a way to 'hard delete' a private channel within 30 days of deletion so that we can create more private channels more immediately?
