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
  • Download detailed implementation plan
  • Phase 1: Mobilization
  • Phase 2: Access Setup
  • Phase 3: SAP Integration Setup (If Applicable)
  • Phase 4: Workflow Development & Testing
  • Phase 5: Go-Live Preparation
  • Phase 6: Production Launch and Hypercare
  • Notes
  • Implementation Timeline
  • Project Roles and Responsibilities

Looply Implementation Plan

PreviousSigning Up & Onboarding Your TeamNextMicrosoft Integration

Last updated 2 days ago

This guide outlines the standard implementation phases for deploying Looply within your organization. Whether you are integrating only Microsoft Teams or extending to SAP workflows, this phased approach helps ensure a smooth, efficient rollout.

Looply provides project templates, onboarding workshops, and technical assistance throughout your journey.

Download detailed implementation plan

Phase 1: Mobilization

Task
Primary Owner

Appoint Customer Project Lead

Customer

Mobilize SAP Basis Team (if SAP integration planned)

Customer

Arrange access to Microsoft Teams Admin Center and Azure Portal

Customer

Confirm Looply Solution Architect engagement (if applicable)

Looply

Phase 2: Access Setup

Task
Primary Owner

Sign up for Looply organization account

Customer

Invite Admins and Developers

Customer

Connect Azure AD tenant to Looply

Customer

Deploy Looply custom app into Teams Admin Center or organizational App Catalog

Customer IT

Schedule optional onboarding workshop with Looply Solutions Engineer

Looply (optional)

Phase 3: SAP Integration Setup (If Applicable)

Task
Primary Owner

Install Looply ABAP Add-on on SAP Gateway

Customer (SAP Basis)

Configure SAP OAuth 2.0 Client

Customer (SAP Basis)

Expose SAP OData and OAuth endpoints externally (direct or via proxy)

Customer (SAP Basis)

Map Azure AD user emails with SAP SU01 email fields

Customer (SAP Basis)

Phase 4: Workflow Development & Testing

Task
Primary Owner

Build initial test workflows (pilot)

Looply/Customer

Design Adaptive Cards for workflows

Looply/Customer

Conduct internal UAT (User Acceptance Testing) with pilot group

Customer Project Team

Looply Solutions Engineer provides best practice review (optional)

Looply (optional)

Phase 5: Go-Live Preparation

Task
Primary Owner

Finalize production deployment plan

Customer Project Manager

Complete internal IT security and compliance approvals

Customer IT / Security Team

Validate error handling, monitoring, and workflow logs

Customer IT / Admins

Phase 6: Production Launch and Hypercare

Task
Primary Owner

Move workflows to Production status

Customer Admin

Announce Looply availability to users (internal comms)

Customer Communications Team

Monitor production workflows for first 2-4 weeks (hypercare period)

Customer Admins / Looply Support (optional)

Hold retrospective and plan for further enhancements

Customer Project Team

Notes

  • SAP-related steps apply only if SAP workflow integration is part of your project scope.

Implementation Timeline

Timelines may vary based on the complexity of workflows, number of SAP systems, and customer internal readiness.

Project Roles and Responsibilities

Role
Responsibilities

Customer Project Manager

Internal coordination, stakeholder updates

IT Admin / Azure Admin

Azure Tenant Connection, App Deployment

SAP Basis Team

ABAP Add-on installation, OAuth setup, Gateway exposure

Looply Solutions Engineer

Technical guidance, SAP/Teams integration support, workflow design best practices

End-User Champions

Pilot testing, feedback during UAT

Looply Support () is available for optional onboarding sessions, integration assistance, and go-live hypercare support.

support@looply.ai

General Integration plan (without SAP Plugin)

SAP Integration plan (with SAP Plugin)

Download Plan.xlsx
Download Plan-SAP.xlsx