Update teamsApp
Namespace: microsoft.graph
Update an app previously published to the Microsoft Teams app catalog. To update an app, the distributionMethod property for the app must be set to organization
.
This API specifically updates an app published to your organization's app catalog (the tenant app catalog).
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ❌ |
Permissions
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.
Permission Type | Permissions (from least to most privileged) |
---|---|
Delegated (work or school account) | AppCatalog.Submit, AppCatalog.ReadWrite.All, Directory.ReadWrite.All** |
Delegated (personal Microsoft account) | Not supported. |
Application | Not supported. |
Note:
- Only Global Administrators can call this API.
- Permissions marked with ** are supported only for backward compatibility. We recommend that you update your solutions to use an alternative permission listed in the previous table and avoid using these permissions going forward.
HTTP request
POST /appCatalogs/teamsApps/{id}/appDefinitions
Query parameters
Property | Type | Description |
---|---|---|
requiresReview | Boolean | This optional query parameter triggers the app review process. Users with admin privileges can submit apps without triggering a review. If users want to request a review before publishing, they must set requiresReview to true . A user who has admin privileges can opt not to set requiresReview or set the value to false and the app will be considered approved and will publish instantly. |
Request headers
Header | Value |
---|---|
Authorization | Bearer {token}. Required. |
Content-Type | application/zip. Required. |
Request body
In the request body, include a Teams zip manifest payload. For details, see Create an app package
Note: Use the ID returned from the List published apps call to reference the app you'd like to update. Do not use the ID from the manifest of the zip app package.
Response
If successful, this method returns a 204 No Content
response code.
Examples
Example 1: Update an application previously published to the Microsoft Teams app catalog
Request
The following example shows a request.
POST https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/06805b9e-77e3-4b93-ac81-525eb87513b8/appDefinitions
Content-type: application/zip
app.zip
For details about the Teams application zip file, see Create app package.
Response
The following example shows the response.
HTTP/1.1 204 No Content
Example 2: Update a new version of an existing app for admin review prior to publication in the current tenant catalog
Request
The following example shows a request.
POST https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/e3e29acb-8c79-412b-b746-e6c39ff4cd22/appDefinitions?requiresReview=true
Content-type: application/zip
app.zip
Response
If successful, this method returns a 201 Created
response code and the key-value pair "publishingState": "submitted"
in the response body. For details, see teamsAppDefinition.
HTTP/1.1 201 Created
Location: https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/e3e29acb-8c79-412b-b746-e6c39ff4cd22/appDefinitions/MGQ4MjBlY2QtZGVmMi00Mjk3LWFkYWQtNzgwNTZjZGU3Yzc4IyMxLjAuMA==
Content-Type: application/json
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#appDefinition",
"@odata.etag": "158749010",
"id": "MGQ4MjBlY2QtZGVmMi00Mjk3LWFkYWQtNzgwNTZjZGU3Yzc4IyMxLjAuMA==",
"teamsAppId": "e3e29acb-8c79-412b-b746-e6c39ff4cd22",
"displayName": "Test app",
"version": "1.0.11",
"azureADAppId": "a651cc7d-ec54-4fb2-9d0e-2c58dc830b0b",
"requiredResourceSpecificApplicationPermissions":[
"ChannelMessage.Read.Group",
"Channel.Create.Group",
"Tab.ReadWrite.Group",
"Member.Read.Group"
],
"publishingState": "submitted",
"lastModifiedDateTime": "2020-02-10 22:48:33.841"
}
See also
Feedback
Submit and view feedback for