Athentra is a Microsoft 365 governance and maturity platform that automates compliance, provisioning, configuration, and lifecycle to keep your tenant secure, compliant, and well‑managed.

Athentra App is the browser-based SaaS for Maturity, Provisioning, Access, Configuration. Athentra Power runs in your tenant (Power Apps, Flows, Dataverse, SharePoint) for Compliance and Lifecycle.

Yes. Athentra can host the app and database in your tenant so data never leaves your region. Setup and updates are handled under a support agreement.

Seven modules: Compliance, Maturity, Provisioning, Access, Protection, Configuration, and Lifecycle; plus supporting features like Tasks, Support, Feedback, Notifications, Approvals.

Yes. Each module has a Power BI dashboard option. Dashboards are optional and require Power BI Pro for viewers.

The Compliance module is one of the core components of Athentra. It continuously scans Microsoft 365 metadata across Teams, SharePoint, OneDrive, and Entra ID, evaluates compliance policies using Power Automate, and records any violations in Dataverse. Automated actions can then be triggered to remediate these issues, ensuring your environment remains secure and compliant.

The module also includes the Athentra Control Centre — a model-driven Power App that provides a unified view of dashboards, policies, violations, and inventories across all connected Microsoft 365 services. It enables administrators and compliance officers to monitor, analyze, and act from a single, centralized interface.

Yes. You can clone or build new Power Automate flows to enforce custom rules using the same Dataverse foundation.

Model → Competency → Capability → Task, with optional Question/Answer pairs for quick assessments.

Templates are fixed or cloned blueprints; Projects are working copies where you record progress, weights, and generate reports.

Yes. Clone the built‑ins and tailor them, or create models from scratch including competencies, capabilities, questions, and tasks.

Use Question/Answer per level within a Competency to gauge current level faster than a full capability review.

Request‑driven creation of Teams or SharePoint sites from admin‑defined templates with approvals and standardized settings.

Yes. Templates can be Public or Private; private templates specify a template audience allowed to request them.

Yes. Templates support predefined channels, tabs, and related settings so new teams are consistently configured.

Reusable setups for permission reviews specifying scope (Teams/Sites), reviewers, frequency, reminders, and entity filters.

An Instance is created and concrete Access Reviews are generated for each scoped resource based on the definition.

They use the Review Assistant to confirm or remove Owners and Members, then approve the review to finalize changes.

Yes. Use the Associated Resource Type and Entity Filter to include all or a subset of resources.

Yes. Configure reminder strategy, lead time before end, and reminder intervals in the definition settings.

Provisioning disables ad‑hoc external sharing; Protection provides a central request process that shares files via a centralized and controlled SharePoint library. External sharing is controlled via approval processes and expiry date.

Yes. Requests must include an expiry date; unlimited sharing is not permitted.

Admins have a centralized and handy view on all shares tenant wide.

A Configuration Package in Athentra is an executable function that allows users to make controlled changes to their Microsoft 365 tenant or generate detailed reports about it.
Athentra’s standard library includes more than 100 ready-to-use packages that cover a wide range of administrative and governance tasks. You can also design your own packages or exchange them with other organizations using Athentra — enabling collaboration and standardization across environments.
For unique requirements, our team can develop customized configuration packages tailored precisely to your organization’s needs.

Package Store contains ready‑made packages; clone them into My Packages to run or customize. You can also build your own packages.

Yes. Export to .ath and import from .ath to move packages between tenants or share with others who have permissions.

A structured process for requesting, designing, building, approving, and promoting Power Platform apps and flows with cleanups and monitoring.

Yes! Scheduled monitoring warns makers and, if overdue, may quarantine or delete assets; reminders are sent automatically.

Athentra uses a modular, per-user, per-month licensing model.
Licensing is based on the number of Microsoft 365-licensed users in your tenant and the Athentra modules you select — each module has its own per-user price.

Depending on which Athentra modules you purchase, certain Microsoft licenses are required to ensure full functionality:

Athentra Dashboards → Each user who accesses dashboards requires a Power BI Pro license.

Compliance Module → Requires one Power Automate Premium license and one Microsoft license that includes Outlook (e.g. Exchange Online Plan 1, Microsoft 365 Business Basic, Office 365 E1, etc.).

Lifecycle Module → Requires one Power Automate Premium license (this can be the same license used for the Compliance Module if both are purchased).

Specific Power Users typically need Power BI Pro if using dashboards; the Athentra Compliance Module requires Power Apps Premium and Power Automate Premium for ONE user; the Athentra Lifecycle Module requires Power Automate Premium for ONE user; a Service Account with Outlook is needed for automations.