Compliance Engine Architecture

PowerRoster Compliance Module ensures your workforce's rostered shifts seamlessly adhere to workplace legislation and policies, saving organisations valuable time to focus on critical tasks.

This article provides a high-level overview of the components deployed in the Azure tenancy as a part of the PowerRoster deployment.

Functional Components

Functional components are conceptual containers. Each container describes a high-level piece of functionality within the PowerRoster compliance solution. The Functional Component diagram is used to simplify deployment diagrams by dividing all the components into smaller containers. The diagram illustrates where each functional component is deployed.

PowerRoster Replicated Data Store – Sync’s PowerRoster data from the Power Platform to an Azure Data Lake using the Power Platform Synapse Link. It also includes the Power Platform TDS endpoint to sync PowerRoster data.

PowerRoster Compliance Engine- Executes a rules engine to detect shifts that do not comply with rules configured in PowerRoster.

PowerRoster Proxy – A proxy for the Power Platform WebAPI endpoint used to write breach notifications to PowerRoster.

Deployment View

PowerRoster Replicated Data Store

• Power Platform Synapse Link - An out-of-the-box Power Platform feature that syncs data from Power Platform (PowerRoster) to an Azure data lake storage account.

• Power Platform TDS Endpoint - The Microsoft Dataverse business layer provides a Tabular Data Stream (TDS) endpoint that emulates a SQL data connection. The SQL connection provides read-only access to the table data of the target Dataverse environment allowing you to execute SQL queries against the Dataverse data tables. Use SQL to query data (Microsoft Dataverse) - Power Apps | Microsoft Learn

• Landing-Data Lake <Storage Account> - Azure data lake storage account used to store synced data from PowerRoster in Power Platform.

• Synapse Workspace - Synapse Workspace instances, used as the destination for data synced from PowerRoster using Power Platform Synapse Link.

• SQL Serverless Database - SQL Serverless database hosted inside Synapse Workspace. The database stores views which are used by the PowerRoster compliance engine to pull data into the PowerRoster compliance engine.

PowerRoster Compliance Engine

• Function App Host <App Service Plan> - An app service plan used to host the function app.

• Compliance Rules Engine <Function App> - Function app containing rules engine function that validates shifts against compliance rules. Additionally, the function app contains helper functions that are too complex and costly to host in the orchestration logic app.

• Orchestration <Logic App> - The Logic app that orchestrates each PowerRoster compliance run.

• Secure Configuration <Key Vault> - Stores configuration that is sensitive, such as app registration secrets, SAS tokens, etc.

• Default Function App Storage (for Rule Engine) <Storage Account> - The storage account used to manage the function app (This is the storage account created when creating a function app by Azure).

• Runtime Cache <Storage Account> - Contains transient cached data in table storage that is used by both the Orchestration Logic App and the Supporting Function App.

PowerRoster Proxy

• Proxy Function App Host <App Service Plan> - An app service plan used to host the function app.

• Proxy <Function App> -A proxy app that writes data to PowerRoster using the Power Platform WebAPI endpoint.

• Default Function App Storage (for proxy) <Storage Account> - The storage account used to manage the function app (This is the storage account created when creating a function app by Azure).