Running Teams PowerShell Cmdlets in Azure Automation
This article describes the prerequisites and how to run cmdlets from the Teams PowerShell module in Azure Automation runbooks. We also consider when you’d want to consider using Teams PowerShell cmdlets instead of Graph API requests or cmdlets from the Microsoft Graph PowerShell SDK. The bottom line is that it’s possible, but maybe not a frequently-used option. https://office365itpros.com/2025/09/12/teams-powershell-azure-automation/From Assignment to Empowerment: How I Deployed Teams Enterprise Voice Using PowerShell
During my last assignment, I successfully implemented Microsoft Teams Enterprise Voice (EV) for a large, diverse user base. With automation via PowerShell, I turned complexity into clarity—delivering seamless communication and routing. This blog shares that experience step by step, including production considerations for a robust rollout. 1.Prerequisites Before you begin, make sure you’ve got: • Teams Phone System license assigned • Access to Teams PowerShell • Installed MicrosoftTeams PowerShell module Install-Module -Name MicrosoftTeams Import-Module MicrosoftTeams Connect-MicrosoftTeams 2.Real-World Experience Our deployment spanned users across globe with varied call routing requirements. Manual provisioning wasn't scalable, so scripting via PowerShell made it possible to: • Bulk-assign direct numbers • Create custom voice routes & PSTN usages • Grant user-specific policies based on department and role 3.Define PSTN Usages Set-CsVoiceRoutingPolicy -Identity Global -PstnUsages "International", "National", "Local" New-CsPstnUsage -Identity "RemoteWorkersUsage" You can customize -PstnUsages based on your organization’s dialing permissions. For example: • "Local" for regional calling • "National" for country-wide calls • "International" for global access 4.Create Voice Routes New-CsVoiceRoute -Identity "IndiaRoute" -NumberPattern "^\+91\10}$"-PstnUsages "Local", "National"-OnlinePstnGatewayList "SBC1.domain.com" 5.Create Voice Routing Policy with PowerShell Before assigning the policy to users via CSV, you need to create the routing policy first. Here’s how: # Create all required policies beforehand New-CsVoiceRoutingPolicy -Identity "IndiaPolicy" -PstnUsages "Local", "National", "International" New-CsVoiceRoutingPolicy -Identity "RemotePolicy" -PstnUsages "RemoteWorkersUsage", "National" 6.Using CSV for Teams Enterprise Voice Provisioning Prepare a CSV file like this: csv UserPrincipalName PhoneNumber VoiceRoutingPolicy Save it as EVUsers.csv. 7.Pro Tips Validate your CSV for trailing spaces or formatting issues. Use logging to track changes with something like Out-File. Add error handling to catch provisioning failures gracefully. 8.Enable Users for Enterprise Voice & Assign Voice Routing Policies #Import users and assign routing policies from CSV $users = Import-Csv -Path "EVUsers.csv" foreach ($user in $users) {# Assign phone number (excluded from Community version) Set-CsUser -Identity $user.UserPrincipalName -EnterpriseVoiceEnabled $true -HostedVoiceMail $true Grant-CsVoiceRoutingPolicy -Identity $user.UserPrincipalName -PolicyName $user.VoiceRoutingPolicy } 9.Validate Your Setup Get-CsOnlineUser | Select DisplayName, EnterpriseVoiceEnabled, HostedVoiceMail Get-CsVoiceRoutingPolicy -Identity "IndiaPolicy" Get-CsVoiceRoute 10.Key Production Considerations Back up configurations before running scripts • Use pilot groups to verify routing behavior • Test number patterns with actual samples • Ensure SBCs are reachable and secure • Communicate proactively with impacted users • Enable audit logging for policy and route changes • Schedule during change windows to avoid service disruption • Collaborate with networking/security teams on QoS and port access 11.Conclusion PowerShell enables rapid, accurate configuration and scalable EV environments. With thoughtful planning and testing, you can deliver a robust Teams Voice deployment like I did. 12.Final Words Whether you're deploying for 10 users or 10,000, this guide—grounded in hands-on experience—can help you deliver a stable and scalable EV environment in Microsoft Teams.
Renewing Teams over PowerShell in bulk / exclude in bulk from policy.
Hey guys, Just recently have turned on group expiration policy for one client, we done a research and it appeared a great idea, however after some time we got a feedback that some teams need to go back to their documents even 3 years after the Teams channel gets created. And here is the question: is is possible to renew Teams / Outlook Groups in bulk using PowerShell? This particular team told us that they got like hundreds of groups, and renewing them even once a year is a pain. Or maybe there is a way to exclude particular Teams from participating in policy? Appreciat eyour help, Kind regards, J
Retrieving SharePoint Site Visitors Using PowerShell Script
I’m working on a PowerShell script to generate a report of Microsoft Teams details, including the owners, members, and SharePoint site visitors. While the script successfully retrieves most of the information, it fails to retrieve the site visitors, which I can clearly see in the SharePoint Admin Center. Issues: Site Visitors Not Retrieved: Despite having site visitors visible in the SharePoint Admin Center, the script returns "Error retrieving Visitors" or an empty string for site visitors. Potential Errors: I'm using a try-catch block to handle exceptions, but it seems like there are no errors being caught that could indicate why the visitors aren't being retrieved. What I’ve Tried: Ensured the SharePoint site URL is correct. Checked permissions and roles for the account running the script. Request: Could someone help identify what might be going wrong or suggest a different approach to reliably retrieve the list of SharePoint site visitors or any module I am missing on? I am using below modules with Powershell Runtime version 5.1. ExchangeOnlineManagement - Version 3.5.1 Get-MsolUserLicences - Version 0.0.8 Microsoft.Graph.Authentication - Version 2.20.0 Microsoft.Graph.Teams - Version 2.20.0 Microsoft.Graph.Users - Version 2.20.0 Microsoft.Online.SharePoint.PowerShell - Version 16.0.25012.12000 MicrosoftTeams - Version 6.4.0 MSOnline - Version 1.1.183.81 PackageManagement - Version 1.4.8.1 PnP.PowerShell - Version 2.5.0 PowerShellGet - Version 2.2.5 SharePointPnPPowerShellOnline - Version 3.29.2101.0 Any insights or recommendations would be greatly appreciated! Thanks in advance for your help. Connect-MicrosoftTeams -Credential $UserCredential -AccountId $myCredential.UserName Connect-ExchangeOnline -Credential $UserCredential -ShowProgress $true Connect-SPOService -Url "https://domain-admin.sharepoint.com # Initialize an empty array to store the results $Result = @() # Get all Teams enabled groups $AllTeamsInOrg = Get-Team $Teamcount = $AllTeamsInOrg.Count foreach ($Team in $AllTeamsInOrg) { Write-Host "Processing Team $($Team.DisplayName) ..." -NoNewline -ForegroundColor Gray $TeamName = $Team.DisplayName $TeamGroupId = $Team.GroupId # Get team details $TeamOwner = (Get-TeamUser -GroupId $TeamGroupId -Role Owner).User $TeamUserCount = (Get-TeamUser -GroupId $TeamGroupId).Count $TeamGuest = (Get-TeamUser -GroupId $TeamGroupId -Role Guest).Name if ($TeamGuest -eq $null) { $TeamGuest = "No Guests in Team" } $TeamMembers = (Get-TeamUser -GroupId $TeamGroupId -Role Member).User $TeamChannels = (Get-TeamChannel -GroupId $TeamGroupId).DisplayName $ChannelCount = (Get-TeamChannel -GroupId $TeamGroupId).Count # Retrieve SharePoint site URL from the team $TeamGroup = Get-UnifiedGroup -Identity $TeamGroupId $SharePointSiteURL = $TeamGroup.SharePointSiteURL if ($SharePointSiteURL -ne $null) { try { # Get all SharePoint Online groups for the site $SiteGroups = Get-SPOSiteGroup -Site $SharePointSiteURL # Find the "Visitors" group and get its members $VisitorsGroup = $SiteGroups | Where-Object { $_.Title -eq "Visitors" } if ($VisitorsGroup) { $Visitors = Get-SPOSiteGroup -Site $SharePointSiteURL -Group $VisitorsGroup.Title | Select-Object -ExpandProperty Users $VisitorsEmails = $Visitors | Select-Object -ExpandProperty Email -join ", " $GroupsData += [pscustomobject]@{ 'Site URL' = $SharePointSiteURL 'Group Name' = $VisitorsGroup.Title 'Users' = $VisitorsEmails } } else { $GroupsData += [pscustomobject]@{ 'Site URL' = $SharePointSiteURL 'Group Name' = "Visitors" 'Users' = "No Visitors Group Found" } } } catch { Write-Host "Error processing site ${SharePointSiteURL}: $($_.Exception.Message)" -ForegroundColor Red $GroupsData += [pscustomobject]@{ 'Site URL' = $SharePointSiteURL 'Group Name' = "Visitors" 'Users' = "Access Denied or Error" } } } else { $GroupsData += [pscustomobject]@{ 'Site URL' = $SharePointSiteURL 'Group Name' = "Visitors" 'Users' = "No SharePoint Site URL" } } # Add team details to the $Result array $Result += [PSCustomObject]@{ TeamName = $TeamName TeamOwners = $TeamOwner -join ', ' TeamMemberCount = $TeamUserCount TeamMembers = $TeamMembers -join ', ' NoOfChannels = $ChannelCount ChannelNames = $TeamChannels -join ', ' SharePointSite = $SharePointSiteURL AccessType = $TeamGroup.AccessType TeamGuests = $TeamGuest -join ',' SharePointSiteVisitors = $SharePointSiteVisitors } Write-Host "done." -ForegroundColor Green }
What happens if you add a user twice to a team using add-teamuser in Powershell?
Hi, I have the following question: In Powershell using the cmdlet add-teamuser, I can add users to a team. But what happens if you add a user twice to a team? Or in other words: What happens, if you add a user that exists already in the team? Would Powershell ignore the action or would it re-add the user? Would this possibly delete what the user did in the team before (for example his posts or his tasks as a pupil)? Should I check first if the user exists already in the course to avoid possible negative affects?Using PowerShell to Post Channel Messages with Teams Workflows
The incoming webhook connector is a popular method to post information to Teams channels, but Microsoft seems set on retiring the Office connectors. The Teams post to channel workflow when a webhook request is received seems like is a possible replacement, but it’s not just a matter of switching mechanisms. Some PowerShell magic is needed to create a suitable adaptive card to post to the channel, which is exactly what we explain how to do here. https://office365itpros.com/2024/06/17/teams-post-to-channel-workflow/Working with Teams Messaging Using the Microsoft Graph PowerShell SDK
This article describes how to use the Microsoft Graph PowerShell SDK to interact with Teams messaging to create new one-to-one and group chats and post base topics and replies to chats and channel conversations. https://practical365.com/teams-messaging-powershell/Sending Urgent Teams Chats with PowerShell
A reader asked if it is possible to script sending chat messages. In this article, we explore how to compose and send Teams urgent messages to a set of recipients using Microsoft Graph PowerShell SDK cmdlets. The conversation with each recipient is a one-to-one chat that Teams either creates from scratch or reuses (if a suitable one-on-one chat exists). https://office365itpros.com/2024/04/24/teams-urgent-message-ps/Modifying the Teams Tenant Federation Configuration with PowerShell
A new parameter for the Set-CsTenantFederationConfiguration cmdlet made me look at the Teams tenant federation configuration again to improve how a script works. Instead of taking all the domains guest accounts came from and adding them to the configuration, I created a function to check if the tenant uses Microsoft 365. If it does, we add the tenant to the allow list in the tenant federation configuration. If not, we ignore the domain. https://office365itpros.com/2024/04/09/tenant-federation-configuration/
