Yes. An internal AI assistant can check the status of Microsoft Teams or Power Automate approvals when it has a controlled connection to the relevant approval records. It can report whether a request is pending, approved, rejected, or awaiting another reviewer. Approval data is operational information, not permanent company knowledge.
Where Approval Records Are Stored
The Teams Approvals app and Power Automate use structured approval records, often stored in Dataverse. Microsoft’s Power Automate approvals documentation explains how approval workflows combine routing with human decisions.
What Questions Could Maisy Answer?
With a read-only integration, employees could ask whether a request is approved, who still needs to review it, why it was rejected, or how long it has been pending.
A Practical Purchasing Example
If a manager approved a $6,800 equipment request but owner approval remains pending, Maisy should state that the purchase is not fully approved and should not be placed yet.
Approval Does Not Always Complete the Process
An approved purchase may still need a purchase order. Approved vacation may still need scheduling. Approved vendor onboarding may still need tax and banking validation. The assistant must distinguish authorization from completion.
Approver Comments Need Context
Conditional comments should remain conditional. Maisy should not convert “approved after Finance confirms the project code” into an unconditional approval.
Permissions and Identity Must Be Preserved
Approval records may contain salary changes, legal reviews, pricing, leave, contracts, or confidential project details. Microsoft’s Dataverse security guidance explains roles and access controls that integrations must preserve.
Can Maisy Start an Approval?
Potentially, through a controlled flow. Starting an approval is materially different from checking one and should require required fields, confirmation, routing rules, and an audit record.
How Pixeldust Connects Approval Data
The Microsoft 365 Knowledge Hub implementation guide explains how SharePoint, Dataverse, Power Automate, Copilot Studio, Teams, and identity controls serve different roles.
During the Pixeldust implementation process, the team defines approved questions, authoritative procedures, permissions, and status distinctions.
The Practical Answer
Approvals record who said yes. The Knowledge Hub explains what that yes allows the business to do next.
