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
  • Microsoft 365 Requirements (For Microsoft Teams Integration)
  • SAP System Requirements (Only for SAP Workflow Integration)
  • Network and Security Requirements

System Requirements

Minimal Requirements, Enterprise Ready

Looply is designed to integrate seamlessly into your existing Microsoft 365 and SAP environments with minimal disruption. Our architecture avoids invasive changes, enabling fast deployment while aligning fully with enterprise security and compliance standards.

This section outlines the required prerequisites across Microsoft 365, SAP, and network layers to help your IT team quickly assess readiness.

Microsoft 365 Requirements (For Microsoft Teams Integration)

Requirement

Details

Microsoft Entra ID (Azure Active Directory)

Required for user authentication, delegated access, and app management

Microsoft Graph API Consent

Admin consent required to grant Looply access to standard scopes for Teams app management and directory lookup

Microsoft Teams Client

Desktop or Web client supported; Looply custom app must be installed via Teams Admin Center or organizational App Catalog

SAP System Requirements (Only for SAP Workflow Integration)

Requirement

Details

SAP NetWeaver Version

750 or higher (compatible with SAP ECC and SAP S/4HANA)

Looply ABAP Add-on

Installation required on SAP backend system

OData Endpoint Exposure

/sap/opu/odata/looply/service_srv/* and /sap/bc/sec/oauth2/token must be externally accessible to Looply's cloud services

OAuth 2.0 Client Setup

Required in SAP Gateway to enable secure, token-based user delegation

Network Accessibility

Outbound HTTPS access from SAP Gateway is required; static IP allowlisting supported if needed

Network and Security Requirements

Requirement

Details

Outbound HTTPS Access

Required from SAP Gateway to Looply's public API endpoints

TLS Encryption

All communication encrypted using TLS 1.2+ standards

IP Allowlisting (Optional)

Static outbound IP allowlisting available for customers enforcing strict egress policies

Authentication Standards

OAuth 2.0 delegated flows supported, including Basic Auth, OAuth Code Grant, and SAML2 Bearer Assertion (OBO) for SAP integrations

If you have any questions about system compatibility or would like assistance with planning your integration, please reach out to support@looply.ai.

PreviousDeployment ModelsNextSAP Integration: ABAP Add-on & Access

Last updated 1 month ago