My Workflow
Teams Deploy Tab deploys Teams apps to the Teams store semi-automatically with the Microsoft Graph API. I only heard about this competition yesterday, and just released the Action now so it's not in use yet. But I'm hoping to use it to drive adoption of GitHub at my company, starting with a custom tab I finished yesterday!
Submission Category:
DIY Deployments
Yaml File or Link to Code
pl4nty
/
teams-deploy-tab
Create or update a Microsoft Teams custom app from a manifest zip file
Deploy an app to the Microsoft Teams app store
Creates or updates a Microsoft Teams custom app from a manifest zip file.
Prerequisites
- Global administrator account (application-level permissions aren't supported)
Setup
- Register an AzureAD application
- Copy the Tenant and Application IDs
- Navigate to the Authentication tab
- Configure the Reply URI as
https://login.microsoftonline.com/common/oauth2/nativeclient - Enable "Treat application as a public client" (at the bottom)
- Navigate to the API permissions page
- Add the Microsoft Graph
AppCatalog.ReadWrite.AllDelegated permission and grant admin consent
Usage
- View the action logs while running (eg https://github.com/pl4nty/teams-deploy-tab/actions?query=is%3Ain_progress)
- Browse to the provided link within 15 minutes
- Authenticate with a global administrator account
- Enter the provided code
Inputs (required)
| Variable | Description |
|---|---|
| TENANT_ID | AzureAD Tenant ID |
| AAD_APP_ID | AzureAD application ID |
| TEAMS_APP_NAME | App display name |
| MANIFEST_PATH | Path to the manifest file |
Example
on: push
name: Deploy to Teams
jobs
deploy
runs-on: ubuntu-latest
steps
- name: …Additional Resources / Info
I've heard from other OSS contributors that the complex deployment process puts them off building Teams apps. Hopefully this Action can help them!
Top comments (0)