adoption
27 TopicsGet all AA/CQ with Resource Accounts
Hello Is it possible to have a script that pulls out all AA/CQ with resource accounts. I would like to pull it to find out which of the AA/CQ do not have resource account. If there is no resource account the field would be empty. Regards JFM_12Solved107Views0likes4CommentsPowershell for creating a Auto Attendant
Hello I would like to create an Auto Attendant through Powershell. The command is New-CsAutoAttendant Teams keeps asking about the DefaultCallFlow. I would like to hardcode the command like this: New-CsAutoAttendant -Name "xx" -LanguageId "fr-FR" -TimeZoneId "Romance Standard Time" How do I add the DefaultCallFlow and then redirect it to an external number Regards JFM_12Solved230Views0likes4CommentsClarification regarding the URL change for 0365 connectors and E.T.A for supporting MessageCards
Clarification regarding the URL change Hi , I noticed the shift from the old URL format to the new URL format for old Office 365 Connectors. After the transition to new URL format in O365 connectors it looks like this : New URL format for 0365 connectors : https://companyadmin.webhook.office.com/... In new MS teams workflows the URL format is this : https://prod-256.westus.logic.azure.com:443/workflows/... We want to differentiate between the O365 connector URLs and new MS Teams Workflow URLs currently if we observe the URLs we can see that for 0365 connectors we have webhook term in the URL and for new MS Teams Workflow URLswe have workflows term in the URL . So that we can use MessageCard or AdaptiveCard accordingly in the mean time for O365 connector and MS Teams Workflows respectively. Can we rely on this logic to differentiate between the O365 connector URLs and new MS Teams Workflow URLs . Will this pattern of using "webhook" for old connectors and "workflows" for new MS Teams Workflow URLs continue to be followed in the future, allowing us to differentiate between legacy and new integrations? Regarding the MessageCard support in new MS Teams Workflows In this https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ it is mentioned that We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025. Could you provide a specific ETA or date for when MessageCard support in the Workflow app will be fully available? We understand more details are expected by March 30, 2025, but we’re looking for a clearer timeline.510Views0likes2CommentsPowershell to export AutoAttendant Default Call Flow
Hello I have written a Script that configures the Default Call Flow. Would like to export before in that same script the existing configuration The part of the script is $autoAttendant_CallFlow = WR_Log_Command -Command { get-CsAutoAttendant -NameFilter $row.AutoAttendantName } -Type "Get AutoAttenand Name" Write-Host "==> This is the existing autoAttendant_CallFlow $($autoAttendant_CallFlow.DefaultCallFlow.Menu) " -ForegroundColor Magenta -BackgroundColor Black But I am getting these results Microsoft.Rtc.Management.Hosted.OAA.Models.AutoAttendant or Account Environment Tenant TenantId ------- ----------- ------ -------- email-address AzureCloud "Tennant" "Tennant ID" Do you have an Idea why it is like that Thank you for your help JFM_12Solved876Views0likes6CommentsSeeking your suggestions on how to modify the UI of the Bot Plugin
Dear Community, I am seeking your suggestions on how to modify the UI of the Bot Plugin. Currently, we are using Adaptive cards to handle plugins with an advanced settings approach(Img 1). However, I recently discovered the MS Copilot Teams App(Img 2), which has a great UI for handling plugins. Unfortunately, I couldn't find any good sources to start a proof of concept (POC) with a similar UI. It would be greatly appreciated if you could share some ideas and resources on how to change the UI to resemble the Copilot App interface Thanks. Img 1 - my bot design Img 2 : Looking for solution588Views0likes2Comments