Our organization has an app hosted on the G Suite Market place however this was created by an admin who is no longer with the organization.
How can you check who 'owns' the app and how can we transfer ownership of the app to an active admin?
Related
I'm making a Slack app (basic webhook for our CI to send Slack updates) to replace one that broke/disappeared when a colleague who created the Slack app left the company. But I realized, won't the app I'm making need to be replaced again when I one day leave the company (since it seems Slack apps are tied to the creator's account)?
So is there a way that I can setup this Slack app independent of my account so that it wouldn't be deleted with my work Slack account?
The best practice to do so is by creating a Service Account.
(Service accounts are a special type of non-human privileged account used to execute applications and run automated services, virtual machine instances, and other processes.)
Use this 'Service Account' for creating new apps and add people working on these apps as 'Collaborators'.
we are running a trading B2B platform were we cannot create testing accounts on a production environment.
Currently we are trying to submit an app to the Microsoft teams catalog, the submission process asks for test credentials to be used to test the app and the connection to the platform alongside the manifest file. however we can only provide sandbox test accounts, which will obviously cannot be used in the production app, and are hosted under different links.
in the manifest to be submitted we setup the production links for the app that needs to be submitted to the store.
The question here is how is this usually handled? how should we provide a sandbox test accounts and a production manifest at the same time for the app submission process?
Basically what Microsoft is asking for is credentials to a test Microsoft 365 tenant, where they can log in and install your app. Your app must for sure already be 100% "production" ready - live hosting etc., not a test setup behind the scenes.
I am using Microsoft Graph API to send messages to private users in Microsoft Teams. I registered an App in Azure Active Directory, gave proper permissions and called the API and was able to successfully send the message.
My question is what would be the most efficient way to deliver this integration to different clients? Do we have to register an App in every azure directory of the client individually, or is there a way I can publish the app that I have created with all the API permissions required and the administrators can install the app in their azure directory
You would have to publish your application in your home tenant as a Multi-tenant application.
When a user from the client's tenant access your app, they will be prompted for login and post that either the user or an admin will have to consent to the app and the required permissions. This will create a service principal in the corresponding user's directory where the consent objects are stored. This way you don't have to register application in each directory.
You can follow the steps listed here for more detailed instructions to convert your application into a multi-tenant app.
Currently, I developing Microsoft ChatBot that needs login via Microsoft Graph.
After I log in the error display as below.
When you registered your app, you chose one of three supported account types:
Accounts in this organizational directory only (i.e. one Azure AD tenant only)
Accounts in any organizational directory (i.e. any Azure AD tenant)
Accounts in any organizational directory and personal Microsoft accounts (i.e. any Azure AD tenant and any personal Microsoft account)
If you chose the first option, your app is not considered "multi-tenant", and you cannot use the "common" endpoint, as the error message indicates. You have two options here:
If your application is to be used by users from multiple organizations, change the intended audience to "Accounts in any organizational directory" (Azure portal > Azure Active Directory > App registrations > Authentication).
If your application is only intended to be used by one organization, then update your code to use the tenant-specific endpoint (i.e. https://login.microsoftonline.com/{tenant-id}/..., instead of https://login.microsoftonline.com/common/...).
I am implementing an integration with Google Drive, which is to show a user's Drive files on our own website (after a 3-legged OAuth2 authorization).
So it is not a webapp that you will connect to the Google Drive UI, and thus I don't see the need to publish it in Apps Marketplace.
My project is created with my personal (free) account on console.developers.google.com,
and I'd like to confirm here: if not published, will it still work with any types of accounts, especially with enterprise accounts(e.g. Google Apps for Work)?
It does not need to be published as long as the domain administrator has not disabled Drive Apps. If a domain admin has disabled Drive Apps, I believe publishing to the Google Apps Marketplace is required so that the domain admin can install the App for all domain users.