Forum Widgets
Latest Discussions
MS Teams access token signature is invalid
I am trying to validate an access token from ms teams in my backend application. The validation fails because the siganture of the token is invalid. This is how I obtain the token: export class MyWebPart extends BaseClientSideWebPart { protected async onInit(): Promise<void> { await super.onInit(); this.context.sdks.microsoftTeams?.teamsJs.authentication.getAuthToken() .then(token => sendToBackend(token)); } } When I copy the token into JWT.io it says that the signature of the token is invalid. I notice that in the token the issuer is: https://sts.windows.net/{{INSERT TENANT ID}}/ and in the openid-configuration: https://login.microsoftonline.com/{{INSERT TENANT ID}}/v2.0 How do I get a proper token?Microsoft.Bot.Connector SendToConversationAsync Failed - 'Forbidden'
Hi. We use Microsoft.Bot.Connector (4.22.9) SendToConversationAsync for sending an activity to a conversation. Most of them are processed successfully, but some fail with 'Operation returned an invalid status code 'Forbidden'. How can I handle it? What is the reason? Also, I have a second question about "blocked conversation." If the user blocks the conversation, I think SendToConversationAsync will fail, too. How can I handle this, and what kind of error will be raised?Creating Workflows is disabled in somewhere
Hi, I was following this guide: Prerequisites to get the the predefined workflow (Post to a channel when a webhook request is received) done. In the next section in step seven instead of having positive sign, I do have a message "Looks like this workflow is disabled by your organization". Anybody knows what other prerequisites the Workflow could have? What else I should have enabled? Somewhere I saw info that I should have "Entra ID \ Logic Apps" enabled, but that is not so clearly stated in anywhere. Something should be enabled (or not locked) in Power Apps site?
Showing intranet sites (Sharepoint) inside teams client
Hi, Im a rookie when it comes to teams-app development, but our organization has a need for custom apps showing different Sharepoint pages to different users. Originally we intended to use Viva Connections, but as of now, it does not seem to fit our needs because we have at least 4 different experiences (School A student, School A teacher, School B student and School B teacher), and we dont want either of them to show the dashboard (we want every user to see its respective Sharepoint site directly because we find it easier to display relevant information here). I have suggested to one of our IT-admins that we disable the default landing page from Sharepoint Management Shell, but they say this will lead to everyone seeing the same default page (tenant-wide). We dont want that, we want all the different types of users to see their respective home site, according to the viva experiences we set up, but without having to load the viva-dashboard first. It may seem mundane, but our (young) users struggle to find our "homesite" this way. As a workaround i figured we created teams custom apps through the developer portal, showing the Sharepoint sites directly. This also allows us to pin both the teacher and student portal for our teachers/staff, which is really handy for easy access. When i created the apps, I added "?app=portals" behind the web content URL in the manifest/app developer portal, so that the home site navigation bar is showing inside the teams app. End goal being they can use the home sites and every sub-site directly in the custom app inside teams. This worked like a charm for a couple of days, but now whenever we use the navigation bar inside the app, it redirects the user to external browser. The frustrating part is that some of my navigation bar links works inside the teams client, but most do not, and sometimes it takes a minute after i start the application where everything works the way i want, where i can navigate the home sites inside teams, but then the teams app suddenly remembers to kick me out into default web browser... Same happens on phone. My problem: My custom teams app (personal tab), redirects user to external browser when clicking links from navigation bar, even though they have the same ourtentant.sharepoint.com domain. My goals: I want to show SharePoint site content inside teams client, without being redirected to browser I want the SharePoint content to be as easy to reach as possible, with the fewest amount of clicks for the 4 different user groups when they open Teams client. Any tips as to how i can reach our goals here? Either through custom apps or through viva?
Help with Deploying AI Agents to Microsoft Teams Chats
Hello, I need help with deploying AI Agents (bots) to Microsoft Teams chats. Here's my current setup: - I have a REST API endpoint that processes user queries and provides LLM-based responses. - Users on my platform can create custom AI assistants. What I need assistance with is: - How to deploy these AI bots into Microsoft Teams chats, allowing end users to create and integrate their assistants directly into Teams. - Any resources or step-by-step guidance on bot registration, deployment, or integrating custom bots would be appreciated. Thank you for your help!CreateChannel in GraphAPI sometimes results in not creating the corresponding Sharepoint/OneDrive
Currently the creation of a channel through the Graph API frequently results in the relative, corresponding Sharepoint folder not being created. When using the Graph API to create a channel the response indicates creating the channel was a success, but when going to the files tab it shows: "Your files can’t be found, working on it to restore them." After having clicked on the files tab in the Teams UI, the folder is created eventually (after a couple of minutes). But because automated processes depend on the channel folder, we don’t want to ask the user to manually open the team before the other processes can continue. So: Team created: Ok -> Channel created: Ok-ish (But missing the linked folder) -> One-drive/share point folder, with the name of the channel: Not created Sometimes the folder is created properly, but lately more often it is not created (Not even after 3-4 days of waiting) until the user opens the files tab in the Teams client. This behaviour is new since it worked flawlessly until a week ago. Is there a known workaround for this?RSC permissions cause app to fail installation in personal scope
I am trying to update an existing up to send notifications. The plan is to use RSC permissions for it. I configured the manifest (v 1.19) with the following scopes: "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Chat", "type": "Application" }, { "name": "TeamsActivity.Send.Group", "type": "Application" }, { "name": "TeamsActivity.Send.User", "type": "Application" } ] } }, I then sideloaded it successfully with this configuration into a team and also into a chat. However when I try to install it into the personal scope directly I get the error in a dialog box: Something went wrong In the network tab of the web inspector I see that this call fails with 403: https://teams.microsoft.com/api/mt/emea/beta/users/apps/definitions/appPackage The body of the response says: {"errorCode":"WebApplicationInfoIdConflictOnSideloadingIntoTeam"} However, when I change the included permissions in the manifest to only TeamsActivity.Send.Group the app installs successfully into personal scope "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Group", "type": "Application" } ] } }, So I guess it has nothing to do with an id conflict. I also made sure to remove all old instances of the sideloaded app before (which was never a problem so far). How can I use all three RSC scopes in my app manifest and still install the app into the personal scope. Or what could be wrong? Anything I could check to figure out why this is not working but only the TA.Send.Group scope?Missing something obvious? Teams App install with custom parameters?
This one is really throwing our team for a loop! We are trying to pass two custom parameters (ID & Token) during app installation Each customer in our application has a unique ID and Token, which we need to pass when they install our Teams bot. We attempted to append these parameters to the installation URL as follows: 🔗 Installation URL: https://teams.microsoft.com/l/app/feea88de-b85f-4a8a-a724-d076d8de24af?source=app-details-dialog&context={id:%20%22%22,%20token:%20%22%22} However, we are unable to retrieve these parameters in the installationUpdate callback. What is the correct approach to pass and retrieve custom parameters (ID & Token) during app installation? Thank you for any insight!
When using proxy on localhost teams fails to establish TCP connection for login
This is a strange problem, and it took us quite a while to get to the bottom of it. We tested on Windows 10 and Windows 11 with the latest Teams app. What is the problem? We are working on a solution the monitors network traffic for a safe school environment. As part of that we install a local proxy on Windows devices. The proxy is configured as manual proxy in the proxy settings. When requesting to sign into Teams, Teams establishes a connection to `login.microsoftonline.com`. Without the proxy that works without problems. Teams establishes a TCP connection, sends a CONNECT, TLS handshake and then encrypted data. When activating the local proxy any connection is fine (e.g. `teams.events.data.microsoft.com`, `nav.smartscreen.microsoft.com` are established just fine), but the one to `login.microsoftonline.com` is not established. In Teams this results in an error page that the login page can't be reached (it reports a 404, but it's not a 404). We ensured that nothing was blocked and there are no lower level connection errors, then we dug deeper with Wireshark. Once accessing the login page (which would trigger connection making for `login.microsoftonline.com`) we see a `SYN` being sent to establish the TCP connection, but there is never a `SYN/ACK`. The local proxy never receives this `SYN` (no connection is ever established), somehow it never reaches the destination but is "dropped". We can see that Teams tries to re-transmit the SYN, but it never arrives at the destination. A tcp `SYN` not reaching it's destination points to it being blocked somewhere, so we: - Turned the firewall off (anything that can be turned off is turned off) - Added specific allow rules for any other device control that could block. This did not help, the problem keeps persisting. (Note: We were able to reproduce this problem with a different proxy solution as well. Once we configure the proxy on localhost we run into this issue.) We also tried: - Configure the local proxy with the IP address of the machine within the local network (i.e. 10.12.128.2) instead of `127.0.0.1`: Leads to the same problem. - Run the local proxy on another Windows machine, turn off firewall and connect to the proxy on the other machine: No problems with this solution, the connection is established fine. We then tried to configure the proxy via PAC file (without a DIRECT fallback), which result in different weird behavior. In the browser the behavior is as expected - pages that are blocked by the proxy report a connection failure, pages that are allowed can be accessed. For Teams login we don't run into problems with the PAC file based settings, but Teams does not route the connection to `login.microsoftonline.com` through the proxy! The connection to `login.microsoftline.com` somehow implicitly bypasses the system wide proxy settings when using a PAC file (i.e. I see the connection in Wireshark, but it's directly established, not going through the proxy even though it is configured via PAC file). Other connections related to Teams are established through the proxy as expected. I don't think this is expected behavior. I have Wireshark traces that show all the different behaviors. If needed I'm happy to add them to this ticket. It would be great to get help with a better understanding what could be the problem. What could cause this behavior (in Teams / in Windows)? With a better understanding of the behavior we could work on overcoming this problem.
Teams app is crashing if window.location.hash it set
We are using the Teams Channel Tab app with a component that replies on the hash parameter. On click of a button from a list of folder within the Tab, we are trying to set the window.location.hash. Another component uses an event listener to listen to the hashChange and retrieves this hash parameter that was set and uses for further processing. This works perfectly fine in Outlook addin as we are rendering the same component in Teams and Outlook However, as soon as I set the window.location.hash, the app crashes without any error in Developer tool Console. We have hosted the Tab app at - "https://localhost:8080/#/channel" I am thinking of 2 possible causes for this crash- 1. Is the app trying to crash when I am setting the hash as it already has '#' in the url? 2. Is there a limitation where we cannot set and get window.location.hash while inside the Teams Tab app?
