Deleting AutoAttendants and CallQueue
Hello There are commands to delete AutoAttendants and CallQueue. But I get allways an error "Can't remove the Auto Attendant. Auto Attendant is still referenced by Endpoints Ids" Even if all Ressource Accounts are deleted a day before. These Auto Attendants and CallQueues are configured as Calling ID's When I manually delete them after removing there also an error that call queue time was to low. Is it possible to force the deletion. Regards JFM_12How to Update Entra ID Apps to Run Teams Cmdlets
MC1134747 describes a new permissions requirement for Entra apps that run Teams PowerShell cmdlets. Despite what you might think after reading some of the overhyped and ill-informed online commentary about this topic, this is not a dramatic security change, and it's easy to update apps to meet the new requirement with PowerShell. First, find the apps that use Teams PowerShell (we show two ways), and then assign the two required permissions to the apps. All done with a few lines of Microsoft Graph PowerShell SDK code. https://office365itpros.com/2025/09/05/update-apps-teams-powershell/New to teams: Are multiple outgoing sales lines possible?
Hey everyone! I am the sys admin of my small law firm, and we officially switch to Teams and Microsoft as a phone provider on September 15th. Currently we use 3cx as our PBX and Callcentric as our provider. Most everything is already set up, and waiting for the port. I already have a reception and incoming sales queue set up with a main auto attendant, basically cloning what we have now. We are noticing that our main phone line is being marked as spam when we call out, likely due to it being our main line and our sales dept is going gangbusters. It was suggested we buy multiple sales lines and switch the number our salesperson is dialing from every so often. What I am wondering is: If we purchase a handful of these numbers, is there an easy way to switch what the outgoing number of our salesperson/sales team/sales queue is showing on outgoing calls and is there a way to have incoming calls from each of those numbers funnel into our incoming sales queue, which is often populated with at least two people? For reference, we will no longer be using 3cx after the 15th so everything is under MS's roof. I also asked copilot hoping it would have some insight, but Im not entirely sure if it understood my situation. Any help is appreciated.
Teams Phone Mobile - Compliance Recording
Hello, I am working on building a compliance recording feature on Teams Phone Mobile. I have a specific scenario where I would like to get inputs from the community. Scenario: Enterprise customer has Teams Phone Mobile solution from the Operator with compliance recording enabled. If for any reason, Microsoft Teams is down the operator has built a capability at network level that the users can continue to do regular mobile calls. Questions: Considering, that the compliance recording is enabled for the Teams Phone Mobile user. Now, since Teams is down the recording bot won’t join the call, but the call still connects without being recorded. This would be a violation. Is this understanding, correct? If the understanding is correct, can this be controlled within the Teams security group policies, or the operator will have to control it at network level i.e. if Teams is down any call does not connect?
Teams Calling Policies Rollout
I have been working on screen pops for inbound PSTN calls, specifically the "Open apps in browser for incoming PSTN calls" & "URL to open apps in browser for incoming PSTN calls" settings in Calling Policies. Is there any documentation on how the whole policy application process works in Teams? It seems to be frustratingly inconsistent. My experiences with updating the link used in calling policies with Windows Desktop clients: During the first production rollout, it took days for some clients to pick up changes to the link. I am logging which pop screen is activated and saw that some picked up the change in a couple of hours, but a few here and there took a couple of days. One lone straggler never picked up the policy change even after having him restart the app, then logout out of Teams and restart. He finally picked up the change after I toggled a policy switch off and on saving twice in between. If picked up within a few minutes. During testing this week, I changed the link in the calling policy, and it did not take effect even after 24 hours on the test clients. I again made a couple of tweaks to the policy, saved the policy, reversed the changes, saved again and within a few minutes, the policy applied to the test clients. A day later, I opened a client using the same Teams account on a different computer and it still had the old policy. Several hours later, it was still using the old settings. Signing out/into teams and restarting the app did not trigger an update to policies. About twelve hours ago, I made a policy change and so far, the client hasn't picked up the change. I shut down Teams, deleted the %appdata%\Teams folder and restarted the app. Interestingly, the %appdata%\Teams folder has not been recreated. Most apps recreate their folder right at launch, but it's been half an hour. The client is still using the old link setting. Questions: Does anyone know if the 24 hours for policies to deploy is for the cloud to deploy, or for the client to check for updates? Does anyone know a reliable way to force a desktop client to refresh policies? Do certain policy changes trigger a more immediate rollout? I seem to remember the Lync/Skype For Business clients having a scheduled update cycle for policies, but there were ways to force it to refresh by deleting files/folders, specific setting or running commands. Testing aside, the fact that a policy change was never picked up in a week by at least one client, makes me wonder how many clients are running on outdated policies that we can't verify.Teams - Camera and screen share issue
Hi, Since yesterday we have been having firm wide issues with camera usage and screen share in Teams calls. When user 1 calls user 2, user 1 can see user 2s camera and screen share. User 2 cannot see user 1s camera or screen share. It seems to be that the recipient cannot see camera feed or screen share, but the original caller can see incoming camera feeds and screen shares. We have tried fully reinstalling and nuking local cache, but no luck. Before we start looking a bit deeper, has any others had this at all. Many thanks guys
PowerShell Permissions
I'm trying to get some data out of Teams programatically via the MicrosoftTeams PowerShell module but I'm having problems identifying the minimum RBAC permissions required to execute commands. I can't find any documentation on what permissions are required to execute a command with anything less than Global Administrator which I'm very against for obvious reasons. The current one that I haven't found any work around for is the Get-AllM365TeamsApps which from what I can tell is the only way to find out the status of all the applications and their status of blocked or unblocked. Is there something I'm missing here or is this not currently documented? Cheers, Ray
Microsoft Teams App in Task Bar shows up as white square after opening app
Using Windows 11 Pro 24H2 (installed on 8/4/2025) with Microsoft Teams: You have Microsoft Teams version 25198.1112.3855.2900. You've got the latest version. It was last checked on 8/15/2025. When I launch the Microsoft Teams App it shows up as a white square icon in the task bar? What can be done to get this icon back to what it was originally. I've used the Microsoft Store to remove this app and install it back again, but does not work. I've also removed the iconchache files stored in: C:\Users\%userprofile%\AppData\Local\IconCache.db.old C:\Users\%userprofile%\AppData\Local\Microsoft\Windows\Explorer\
