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: Not receiving the token response from MSAL Acquire a token silently from the MS Teams Iframe #222 acquireTokenSilent not working inside Teams app? I tried to enable MSAL's debug logging info. Working fine stand-alone; inside Teams: not one log message. There seems to have been a lab demo 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 client "Loading Microsoft Teams" issue TM236316
1/29/2020 4:30 PM PST Edit: (Official documentation for this issue has been released under the M365 Admin Center - Service Health Dashboard message (TM236316)). Please use that message (which is marked below) as the formal communication of use. Title: Some users that utilize the same username with work/school and personal Microsoft account can't launch Teams desktop app User Impact: Users may be unable to launch the Microsoft Teams desktop client. More info: Affected users may see a message that states, "Loading Microsoft Teams"; however, the client does not load. Affected users may be able to load Microsoft Teams in compatibility mode as a workaround. Alternatively, the Microsoft Teams web client works as expected. Users with the same email address for their work and personal account can rename their personal account by following the instructions described here: https://go.microsoft.com/fwlink/p/?LinkID=733247 Current status: Our short-term mitigation and long-term remediation efforts are progressing as intended. To prevent further impact from occurring in new downloads of the Teams desktop client, we've updated the Teams download page with a prior build to prevent further recurrence of this issue for any future downloads. As a longer-term fix, we are currently testing and validating the effectiveness of an updated build. This process is progressing as expected and we estimate that the new build will be ready for deployment early next week. In parallel, we're continuing to develop and test an additional fix that will update users' current version, as well as automatically remediate the issue for any user that is in an impacted state. While this work is underway, users with the same email address for their work and personal accounts have the option of mitigating impact by navigating to the teams.microsoft.com/downloads page, uninstalling the client, and redownloading the updated version. Scope of impact: Impact is specific to users utilizing the same username with work/school accounts and their personal Microsoft account. ================================================================== Hello everyone, We've identified a bug on the latest desktop app build that prevents a small number of users from signing in, as users would hit an issue loading the client similar to the following screenshot: This issue only affects/affected users who use the same username with their work/school account (AAD) and their personal Microsoft account (MSA). Any currently affected users should uninstall Teams and download it again from https://teams.microsoft.com/download or use the Teams web app while we resolve the issue. Note, if you're currently using the same email address with a work and a personal account, Microsoft recommends renaming your personal account as described here: https://go.microsoft.com/fwlink/p/?LinkID=733247. #GoTeams Sam Cosby, Teams Engineering PMMSTeams Desktop Client Authentication : Popup not showing [Angular @microsoft/teams-js: 1.8.0]
Hi There, microsoftTeams.authentication.authenticate works perfectly on teams web client but not working on the teams desktop client, Tried many workarounds suggested by ms community, async, using promises but nothing is worked. calling authenticate following microsiftTeams.initialize() is opening a browser tab instead of a desktop client popup Any workaround for this? Is there a way to debug MS-teams desktop client? Teams SDK : Pernille-Eskebo/teams-js: 1.8.0 Angular 8 microsoftTeams.authentication.authenticate works on web client but not on the desktop client
graph toolkit SSO without Login Component
in my teams tab i have followed the below link and authenticated Teams Tab. https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso I want to able to use graph tool kit with out Login component as i have sso for tab, is it possible to do so? if so can i call the graph toolkit components
