Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Quick Deployment
  • Forcing Admin Approval
  • Manual Installation
  1. App Management
  2. Deploying apps to Teams App catalog

Looply Dashboard

Deploy Teams apps to your organisations Microsoft landscape with ease using Looply

PreviousDeploying apps to Teams App catalogNextManual Installation

Last updated 5 months ago

Once you have created your Teams app using Looply, you'll need to deploy it to your organisations Microsoft landscape in order to make it available for your users to install and unlock remote app management.

Quick Deployment

Note: You will need to integrate a Microsoft account from your organisation that has the appropriate privileges required to publish a new app to your landscape with Looply before continuing.

Versions of your Teams app can be seamlessly deployed to your Microsoft organisation once they have been populated with all required information and in the Ready status.

To deploy your app, Go to App Manager -> click the Deploy button located at the top of the Create/Edit app page.

You'll need to confirm which Microsoft integrated account you wish to use for deployment by selecting it and clicking Deploy again in the side panel.

If you can't see the correct Microsoft account within the side panel window, we recommend disconnecting and re-connecting your integration.

Once your deployment is complete, you can verify it has worked correctly by going to Microsoft Teams and viewing the integrated app catalog.

Forcing Admin Approval

Looply supports the ability to force your custom Teams app to require approval from an organisation administrator when deployed in your Microsoft landscape.

This can be useful when you want to have your deployment approved by another party before going live to your users.

You can enable this functionality by toggling the App Requires Review switch on from within the Settings tab of the Teams app you are creating or editing.

Manual Installation

Users can also perform a manual installation of their app using the ZIP file available when creating or editing an app. This can be useful for testing purposes, or if you explicitly do not want your app to be available in the Teams app catalog for all users.

Downloading ZIP

You can download your Teams app as a ZIP file by clicking the Download ZIP button.

These files will contain:

  • Color Icon - PNG file for your chosen color icon image

  • Outline Icon - PNG file for your chosen outline icon image

  • Manifest - Generated manifest JSON file containing the details of your app

Uploading ZIP in Teams

Once you have the ZIP file of your app, you can move to Microsoft Teams to upload and install it.

From within Microsoft Teams:

  1. Select Apps from the left sidebar

  2. Choose Manage Your Apps

  3. Click Upload an app

  4. Select Upload a custom app

  5. Choose your ZIP file

Your custom Teams app should now be successfully uploaded and installed within your Microsoft Teams client.