Skip to content

Technologies Used

This page summarizes the technologies IMPACT 365 uses. It is intended for security review, procurement, and technical approval—not as a deployment or implementation guide.

Microsoft 365

  • SharePoint Online — Portal site for configuration, workflow queue, request lists, templates, and audit/compliance data. All IMPACT metadata and job state live in SharePoint.
  • Microsoft Teams — Workspaces can be provisioned as Teams-backed sites; activity reporting uses Teams-related data from Microsoft Graph.
  • Microsoft Graph — Used for usage reports, activity data, and email notifications. Access is scoped to what the automation needs (e.g. reports, mail send).

Azure

  • Azure Automation — Runs the automation that processes workflow jobs. Uses managed identity where possible for secure, credential-free access to Azure and Microsoft 365.
  • Azure Storage — Used for storing template files and temporary report data as part of the automation pipeline. Data is tenant-isolated.

Power Platform

  • Power Apps — Can be used to build request and admin interfaces that create or update items in the IMPACT portal (e.g. workspace requests, workflow jobs).
  • Power Automate — Used to trigger automation when new jobs appear in the workflow queue and to run scheduled flows that create recurring jobs (backup, audit, compliance, etc.).
  • Connections — Standard Power Platform connections are used to call Azure Automation from flows; these are configured during implementation.

Authentication and security

  • Managed identities — Automation runs under an identity that does not require stored passwords where supported (e.g. Azure Automation managed identity).
  • Application permissions — Where Graph or SharePoint are accessed by automation, least-privilege application or delegated permissions are used as appropriate.
  • Configuration — Sensitive values (e.g. list IDs, connection details) are stored in configuration lists or secure configuration; they are not hard-coded in client-facing documentation.

Data flow (summary)

  • In — User requests and scheduled triggers create items in the workflow queue; configuration and templates are read from SharePoint.
  • Process — Azure Automation runs the workflow engine, which routes each job to the right capability (SharePoint/PnP for most operations, Graph for reports and email).
  • Out — Results and status are written back to SharePoint; optional email/Teams notifications are sent via Graph. Backup and report artifacts are stored in designated libraries or storage.

Compliance and sovereignty

  • Processing runs within your tenant and designated Azure subscription.
  • No third-party SaaS is required for core IMPACT logic; the solution uses Microsoft 365, Azure, and Power Platform only.
  • Your organization retains control of data residency via Microsoft 365 and Azure region selection.

For deployment details, infrastructure sizing, or exact permission sets, work with your IMPACT 365 provider.