Installing Power IMS as a Teams app – step by step

    How to upload a Power IMS module as a Microsoft Teams app, test it with demo data and evaluate it within 30 days – including prerequisites, permissions and SharePoint data storage.

    M365 in practice24 August 20269 min read

    Why Teams apps are the fastest way in

    Introducing a management system used to mean project proposals, servers, interfaces and training. With Power IMS every available module – Power QMS, Power Audit, Power Maintenance, Power CI, Power Safety, Power Risk and the free Power Hub – runs as a native app directly inside Microsoft Teams. All data stays in your own SharePoint.

    Prerequisites

    • A suitable Microsoft 365 plan per user: Business Standard, Business Premium or Microsoft 365 E1/E3/E5. These plans include Teams and SharePoint Online.
    • A Microsoft 365 administrator (e.g. Teams admin or global admin) allowed to upload custom apps.
    • No additional Power Platform licences. Those are only required for the Power QMS for Power Platform variant.

    Trial version in your tenant

    Because deployment in your Microsoft 365 tenant is more involved due to security requirements, we set up the trial together with you. After a short call you get a 30-day trial including sample data – with no obligation.

    1. Book a call – We discuss your modules and the right SharePoint storage location.
    2. Installation – We install the app in your tenant and connect it to your SharePoint.
    3. Load seed data – We add sample data so you can start right away.
    4. Short onboarding – In 30 minutes we show you the most important features.

    The rest of the app is explained inside the app – no parallel documentation needed.

    Where does the data live?

    All content – documents, audits, actions, risks – is stored in SharePoint lists and libraries inside your own Microsoft 365 tenant. No additional data silo is created at an external provider, and existing governance rules such as retention, backup, sensitivity labels and access rights continue to apply unchanged.

    Making the 30 days count

    A trial is meaningful when it is more than clicking around. A proven approach:

    • Week 1 – Installation, demo data, feature overview with two or three key people.
    • Week 2 – Map one real process of your own (e.g. an internal audit or five controlled documents).
    • Week 3 – Test roles and permissions: who may approve, who may only read?
    • Week 4 – Evaluation: does the scope fit, which adjustments are needed, which modules come next?

    Common pitfalls

    • Custom app upload is blocked. In many tenants the policy is disabled by default. Your Teams admin can enable it for a test group.
    • Testing in a production team. Use a separate pilot team during the trial so production channels stay untouched.
    • Demo data in live use. Remove the demo data before you start working with real content.

    After the trial: configure, validate, go live

    After the trial come configuration to your processes, roles and templates, validation in a pilot area, and finally productive use with migration and training. Installation and base configuration are included in the licence fee.

    Exception: Power QMS for Power Platform

    Power QMS is additionally available as a variant for the Microsoft Power Platform. This variant is not shipped as a Teams package; it is set up together with us in your Power Platform environment and requires Power Apps Premium and Power Automate Premium.

    Written by the Power Manufaktur team – specialists for quality management and Microsoft 365 based management systems.

    Ready for the next step?

    Book a free 30-minute consultation – we discuss your requirements and show what is possible with Power IMS.