The Challenge!

Microsoft Teams provides an easy entry into the world of digital collaboration.
However, Teams cannot be created in a fully automated way, from application to embedding in a lifecycle process. As soon as a critical mass of teams is exceeded, the overview and structural setup is lost, which is not desirable from a user and administration perspective. Our product closes this gap and helps you to get a better overview.

  • In-house processes from application to the lifecycle of a team cannot be conveniently automated.
  • It is difficult to assign teams to a specific information landscape within the company.
  • Status, cost centers, project numbers and other information cannot be assigned to a team.
  • There is no reference to relevant processes and applications.
  • From a compliance perspective (e.g., ISO 9001), unambiguous keywording of resources is also an important key to greater clarity.
  • In administration, teams can only be distinguished by their name and their member list.
  • External systems, e.g. service desk, purchasing or project portal, can only be integrated with increased effort.

Can we help you further?

Do you have questions or need more information?
Get in touch now.

Our Solution

With our product, we go one step further than existing solutions on the market.
We extend your Teams landscape with metadata that can be individually extended by you, allowing you to easily map your company structures, processes and other information. Teams Spirit is a flexible construction kit that enables you to adapt the management of your Teams landscape individually to your company without having to make any compromises.

In this way, you always maintain an overview of your content despite complex IT architectures.

Give your users an easy way to create new teams. Define which categories are necessary when creating, whether approval is required, and which template should be used to provide content.

Form for creating a new team

Assign additional information

A simple form engine helps users request the right content. With an integrated approval process, we help you target content delivery.

Through integration with PowerAutomate, approval for the new team is obtained directly through a request in a Teams channel.

Teams Spirit example

An innovation manager wants to create a team for a product innovation. Assigning metadata helps her with categorization, cost center assignment, and subsequent confidentiality classification.

Users are provided with a simple app within the Teams environment.

With this they can:

  • request new teams within the given structure
  • View existing teams and filter them according to specific criteria
  • View and modify metadata

By structuring the teams, your employees have the overview.

Teams Spirit Example

A project manager needs a new project team. He chooses the right template and assigns metadata for cost center, department and confidentiality. The team is automatically set up and channels are created in advance according to the template.

Since it is a secret/confidential project according to the categorization, external users are excluded and the team is not displayed publicly.

View with additional information

Filterable overview of available teams

From a process point of view, the creation of a team is often not the end. For projects with time-limited resources or certain statuses, further trigger-based processing can be important even after creation (automatic archiving, final reports, workflows, third-party systems, etc.).

Teams Spirit Example

A project manager sets the status for a project to “completed”. The final report is automatically requested for approval by a workflow and the team is then archived.

Approval from the owners to archive the team is still obtained through the PowerAutomate interface. Before archiving, all external guests are removed from the team.

*Definition of rules and actions for automated processes

Large Teams inventories can now be easily viewed and edited thanks to the additional integration of metadata. In doing so, we rely on software standards and enable you not to lose the administrative overview.

Third-party systems can be addressed in both directions via our application programming interface (API). In this way, Teams integrates seamlessly into your application landscape.

Teams Spirit Example

The internal purchasing department orders an automatic provision of project resources (Teams, MS Project Site etc.) from the internal purchasing portal.

The development department connects the systems either via the REST API or our PowerAutomate Connector and Teams Spirit takes over the automatic creation of the project environments via a workflow.

Can we help you further?

Do you have questions or need more information?
Get in touch now.



  • Form engine for requesting and approving new installations
    • also controllable via REST and PowerAutomate
  • Templates according to PnP standard
  • Apply sensitivity labels to templates
  • specify individual expiration dates
  • Preset metadata sets
  • Clone content
    • Planner
    • OneNote
    • SharePoint Site
    • Settings
    • Channels


    • Provisioning
    • Object changes
    • Automations
    • Actions
  • Power Automate Connector
    • Trigger:
      • Trigger can be triggered via rule
        • when a team has been requested
        • changed metadata
        • guest was added
        • and much more
      • Free configuration of data transfer
    • Actions:
      • All important actions from Teams Spirit from
        • Permissions
        • Create teams
        • Change metadata
        • and much more


  •  Trigger
    • New requests
    • Metadata
    • Delta List
      • Changes within groups
        • Example: Adding a guest
      • Deleted or archived teams
    • API (incoming REST calls)
  • Rules
    • All known comparison operators
      • Metadata
      • Group object
    • Date processing
  • Actions
    • Adapt standard fields of a group (name etc.)
    • Modify metadata
    • Add or remove users
    • Remove guests
    • Archive teams
    • REST calls to third party systems
    • PowerAutomate integration with Custom Connector


  • Customizable tags
  • Based on Microsoft’s Open Schema standard
    • Usable in all Graph based applications
  • All important data types
    • Text
    • Numbers
    • Date
    • Yes/No
  • Freely configurable metadata per template
  • Subsequently changeable
    • also via REST and PowerAutomate
  • Integration as tab in teams

Can we help you further?

Do you have questions or need more information? Get in touch now.

Immanuel Fuchs

Phone: +49 (40) 53 79 87 50-0

Your contact for solutions based on Microsoft 365 and SharePoint

    * Mandatory fields