ms teams app not listed in publish to org page - microsoft-teams

The app is approved and published to org. But in this page it's not visible.
You can see the bot is approved.
There is no user level policy restriction or anything. There is only one user and its admin.

Related

How user can install app from the team app store without admin approval

How user can add the app in MS Teams, without Admin approval?
So, my question is what policy needs to be added or removed to get rid of the below message:
I am the admin of the tenant and I want my users to install this app if they wish to do so.
If you're a global admin, you can review, and grant consent to apps that request permissions on behalf of all users in your organization.
To grant org-wide consent to an app, follow the steps which mentioned in following document:
https://learn.microsoft.com/en-us/microsoftteams/app-permissions-admin-center#grant-org-wide-admin-consent-to-an-app

Teams Toolkit SPFX Application not rendering for accounts without Teams Admin or Global Admin

I created an SPFX application with the Teams Toolkit that utilises Microsoft Graph API to get data,after packaging and deploying the manifest folder to Teams Admin Center, it renders well with accounts that have Teams Admin and Global Admin access but accounts without this access are unable to access the application as it shows an error as seen in the image.
The Component ID and version in the message are speaking to the React-dom component id and version in the project.
Please i need suggestions on how to resolve this as i am not sure if its just a permission issue
I have tried updating my spfx version but that didnt work as i was already working with the required version of spfx and all other dependency versions
You can raise an issue in https://github.com/OfficeDev/TeamsFx/issues so we can support you better.
I tried to reproduce your issue but failed. The web part displays successfully for account without Teams/Global Admin in my side. Let's clarify the steps before the issue happens:
Create a SPFx project in Teams Toolkit and utilizes Microsoft
Graph API to get data
Click 'Provision in the cloud' to provision
the Teams app (with Teams/Global admin account)
Click 'Deploy to
the cloud' to generate the sppkg and deploy it to SharePoint (with
Teams/Global admin account)
Click 'Publish to Teams' to publish
the Teams app manifest in Teams app catalog (with Teams/Global admin
account)
Approve the submission in Teams admin portal
Install
and open the Teams App in Teams with Teams/Global admin account and
the web part displayed successfully
Install and open the Teams
App in Teams without Teams/Global admin account and the web part
shows error.
Could you help confirm whether you're having the steps above to reproduce the issue?
BTW, after deploying you should be able to use the web part with normal account in regular page in SharePoint. Maybe you can check whether everything is OK in SharePoint app catalog
SPFx solution after deploy to SP app catalog

Microsoft Teams Manifest: can contentBotId be of different tenant

I am trying to use contentBotId (Azure bot ID) in my MS Teams manifest file.
https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema-dev-preview
When it is from same tenant that of MS teams domain (xyz.com) then its working and loading the data
But when its from different tenant, then MS Teams is not loading anything
{errorCode: 0, message: "<BadArgument>Unknown bot"}
Is there any restriction on this?
Before creating the MS bot, using ML Studio, create multi-tenant bot for perfect App registration.
Follow the procedure to create the bot and register the application.
By mentioning all the required. Check the manifest file for the required ContentBotId. Test the URL after app registration into multi-Tenant.
If still the error occurs. We need to setup the connection settings under configurations.
By adding Oauth connection settings we will get some kind of authentication for different clients for the same authentication URL (website URL).
Able to resolve the issue.
Yes it can be from different tenant.
when we use existing AAD instead of creating from Azure bot template, this issue occurs. Seems like MS Teams is not able to find this AAD/ or Bot Handle.
Root Cause (Might be): Manually created AAD have email address of user who have created this in Owners section (screenshot 1), while AAD created from Azure bot template have "Bot Framework Dev Portal" user (Screenshot 2).
And I am unable to add this user by searching.
Screnshot 1
Screenshot2

how to display slack app information such as clientID

am not able to retrieve the App basic information for slack-app developed by another member in my workspace
after accessing api.slack.com/apps only my own apps are displayed, how I can retrieve other apps developed by another member in my workspace.
I was expecting to display all apps owned by my workspace
only my own apps are shown
Due to the security architecture of Slack you can not see the app details like its client ID unless you are the owner of the app or the app owner has granted you permission. Your role on the workspace (e.g. admin) does not matter in that regard.
App owner can add additional collaborators for their app. Those collaborators will have the ability to see all details of an app incl. the client ID.
See also this topic:
Best practice to manage app ownership in Slack

Microsoft app ID under the bot service on Azure

While creating Microsoft app ID under the bot service on Azure, encountering message as "Insufficient privileges to perform this operation. Please ask your administrator to allow users to register applications".
I am using free trial subscription of Azure. How to resolve this issue?
You lack permissions to create application registrations in your company's tenant.
This page has information on what this means.
To summarize so you don't have to read that whole page:
In the Azure Portal, go to your Active Directory tenant.
Click on 'Users and Groups'
Select the 'User Settings' blade.
Under 'App Registrations' see if the setting 'Users can register applications' is set to 'Yes' or 'No'.
It is probably set to 'No'
Your company's Active Directory admin will need to change this setting to 'Yes' in order for you to register your bot app under your company's tenant.
The other option is to have you AD admin register to bot for you and provide to AppId and App Password that is generated.

Resources