Publish teams bot only to some customers
We have a teams bot that we would like to be installable only by our customers. Is it possible to publish a bot to the teams store and only allow a set of organization / people install it ? As far as I know, bots published to teams store are public and installable by anyone."You'll need a new app to open this about link"
I have a custom app running inside of Microsoft Teams. Everything works as expected when running it inside the Teams web application. Running it inside the Teams desktop application breaks part of my custom app. The issue arises when making a request to any web API. That could be the Microsoft Graph API or a custom one I've build for the custom, client application. Instead of getting data back when making the request, I get a popup stating "You'll need a new app to open this about link". Look for an app in the Microsoft Store. Yes/No. I've tried all kinds of different things. Different providers, SSO vs Azure Auth. Any help would be highly appreciated. Regards, Tolga
How do I get my teams bot to authenticate to a web service
I have a teams bot which I want to use as an interface for my service stack webservice however the token I have access to is not being accepted by the web service. I followed the "AAD SSO for tabs and message extension" tutorial to set up my Azure instance and get a basic bot up and running. When I modified the query handler to send a request to a web service with the token provided it is responding with a login page. This is the code that I added to the Simple Graph Client in a new method which passes in what the user types as query HttpWebRequest request = (HttpWebRequest)WebRequest.Create("https://<my website>/api/ws/v1/search?query=" + query); request.Headers.Add("Authorization", "Bearer " + _token); request.Method = "GET"; request.AutomaticDecompression = DecompressionMethods.GZip | DecompressionMethods.Deflate; using (System.Net.HttpWebResponse response = (HttpWebResponse)request.GetResponse()) using (Stream stream = response.GetResponseStream()) using (StreamReader reader = new StreamReader(stream)) { return reader.ReadToEnd(); } Do I need to make use of a shared certificate? or is there some additional configuration that I have missed which is necessary to make this situation work?Login Prompt when requesting 3rd public API
I have custom Tab app. I am able to get the Teams context. I've also implemented SSO, so all mgt components are working fine. I have a custom ASP.NET Core WebApi (v6). It does NOT require authentication. I've decorated the controller method with [AllowAnnonymous]. I've tested the endpoint in browsers and Postmost. All good. Back in my custom Teams Tab app, I make a request to aforementioned API endpoint. It looks like this: https://localhost:44332/Test As soon as I make the request, I get a popup to login.microsoft.com. Why? What am I missing? Thank you, TolgaTeams Desktop not allowing request to protected Azure WebAPI
Scenario I have a simple application setup. An Angular SPA front-end and an ASP.NET Core WebAPI. The Angular front-end application has been registered and loaded into Microsoft Teams. One of the Angular app's features is to request data from an Azure hosted ASP.NET Core WebAPI. The WebAPI is protected using Microsoft Identity Platform. Issue In the Microsoft Teams WEB application all is worked as expected. The SSO service I've created works and MSAL in the Angular App is picking up the access_token and successfully authenticates to the ASP.NET Core WebAPI to retrieve the protected payload. WHY IS THIS NOT WORKING INSIDE THE TEAMS DESKTOP APPLICATION? What does work is making a request to a PUBLIC (un-protected) webapi. But for PROD, this is NOT an option. Please help! I've been working on this for too long. Regards, Tolga
MSAL vs. Microsoft Teams
As ADAL hasn't been touched in over two years now, I have migrated my application to MSAL. Sadly enough the Teams docs are still ADAL based. I have an application that is working fine outside Microsoft Teams. Once I embed it as an app inside Microsoft Teams, two things happen: MSAL's acquireTokenSilent method, which returns a promise, fails silently without any possibility to know what happened. This has been raised before, many times: https://github.com/OfficeDev/TrainingContent/issues/606 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/222 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/470 I tried to enable MSAL's debug logging info. Working fine stand-alone; inside Teams: not one log message. There seems to have been https://github.com/OfficeDev/TrainingContent/blob/master/Teams/04%20Fundamentals%20of%20Microsoft%20Teams/Lab.md#exercise3 with MSAL's acquireTokenSilent in it, but that probably worked because it was launched from the config screen (or elsewhere) and not from the tab. So on what location would acquireTokenSilent work? Should we move it to such an authentication popup to get it to work (far less silent though).Teams custom personal app (SPFx) - slow authentication startup in desktop app
Hi We've implemented quite some Teams personal apps at clients now and the custom Teams apps in the (Teams desktop app) sometimes have load times ranging from 4s - 10s before our custom code even begins. The Teams web app handles auth in a different way, so never any issue there. It appears to have something to do with the way authentication is done in the desktop app (acquire OBO token call...). With a trick, you can also get the console & network tab to show in the desktop app. That way we can verify when our React is loaded & starting + when our backend api calls are done. Clients are complaining about the response times and rightfully so. The response times before our code hits also varies greatly between tenants as mentioned. Has anyone had the same experience? Is there a magic wonder solution out there that I don't know of yet (e.g. simple AAD authentication setting) ?
