Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

 You're right! Since AzureAD and MSOnline modules are deprecated, you need to use the Microsoft Graph PowerShell SDK to retrieve the group ID. Solution Using Microsoft Graph PowerShell You must have a M365 group created first and define the membership :  Allowed Group Creators . 1. Install and Connect to Microsoft Graph PowerShell If you haven't installed it yet, run: Install-Module Microsoft.Graph -Scope CurrentUser Then, sign in with an Admin account : Connect-MgGraph -Scopes "Group.Read.All", "Directory.ReadWrite.All" If prompted, grant admin consent for the required permissions. 2. Get the Security Group ID Since Get-AzureADGroup no longer works, use this instead: Get-MgGroup -Filter "displayName eq 'Allowed Group Creators'" Copy the Id from the output (this is the Object ID needed for the restriction). 3. Apply Group Creation Restriction Run the following PowerShell commands to modify the Microsoft 365 Group Crea...

Handling Inbound Call Routing with Microsoft Calling Plans Inbound Call Routing with does not work with Microsoft Calling Plans ! This only works with Direct Routing , meaning a voice route on a  SBC . The reason is that Microsoft Call Routing only handles outgoing calls. Set-CsOnlineVoiceRoute: Modifies an online voice route. Online voice routes contain instructions that tell Microsoft Teams how to route calls from Microsoft or Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX) . Here possible scenario: Here are some configuration setup Microsoft assigned phone numbers from +4912345600 - +4912345699  What we want to archive is: The number range from +4912345600 - +4912345649 for incoming calls must be route to +4912345610 .  Within this range, dedicated numbers are assigned to some users If they make a outgoing call, the outgoing number must be displayeed as +4912345610.  The number +491234561...

Outlook New is not automatically defined in the autostart routines. Therefore, you must add it manually. Start the Windows Taskmanager, with Outlook New running and locate the Outlook Main Task. Right click and open File Location. Next, press Windows Key + R and type :" shell:startup ". This opens the startup location folder. Align both windows and right click and drop the Outlook New file (OLK.EXE) from it's location into the startup folder. Chose the "create shortcut" option. You successful completed the task and Outlook New will startup during your next login/ reboot

How and when to decommission your on-premises Exchange servers in a hybrid deployment | Microsoft Learn I provide you the link and a simple answer Running Exchange Online ONLY with Active Directory (Entra ID Connect): NOTE: You do NOT need a running Exchange Server on-premises, but the NEW Exchange Management Tools Move the LAST Exchange Server onto a Virtual Machine ShutDown the VM and archive the Exchange VM Delete the VM executing CleanupActiveDirectoryEMT.ps1 is optional (if you would need an Exchange Server later, you can re-deploy with \ADPrep) Install the NEW Exchange Management Tools on any Windows Machine you need (Windows 11 is supported for Exch Mgmt Tools) do NOT modify Entra ID Connect, leave all Exchange hybrid configurations inplace (if you like to fully remove Exchange On-Premises, you can do so, but you must modify Entra ID Connect msExch attribs not to be sync'ed at all. Your users must be managed locally and you need to set the mail and proxy Address manually in...

This is an know bug within Teams. This issue is happening on desktop and mobile version only, if you had installed the Teams app before and changed / created a new Microsoft M365 Tenant with the same user name (UPN/ SIP) Solution: Uninstall Teams App Delete all Teams references and folders Reinstall Teams App Login normally

 Teams Federation isn't working. The Get-CsTenantFederationConfiguration will show the current settings of your federation setup. Nevertheless, if you are owner of an Microsoft TRIAL tenant, federation with other tenants isn't working automatically any longer. Microsoft had introduced an new parameter: -ExternalAccessWithTrialTenants "Blocked"  Therefore, all Microsoft Tenants have the new DEFUALT setting "Blocked" defined. Your partner organization must remove "ALLOW" the federation with you. This also impacts all Microsoft MVP Tenants with only MVP assigned licenses. Note a side: The RUN TEST diagnostic will provide you with false positives here: https://aka.ms/TeamsFederationDiag IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities - Microsoft Teams | Microsoft Learn