Summary
Microsoft Power Automate is a flexible, low-code automation tool available to all Michigan Medicine faculty and staff. Each automation, or flow, consists of "triggers" that kick off the automation, "actions" that are performed on data through interconnected logical steps, and "connectors" to other applications, databases, and systems. This article presents a brief summary of the connectors that are currently available in the MM environment.
Body
Summary
Microsoft Power Automate is a flexible, low-code automation tool available to all Michigan Medicine faculty and staff. Each automation, or flow, consists of "triggers" that kick off the automation, "actions" that are performed on data through interconnected logical steps, and "connectors" to other applications, databases, and systems. This article presents a brief summary of the connectors that are currently available in the MM environment as of early 2026.
Note: the connectors available in the U-M (campus) environment may differ and are not covered in this article.
Details
Types of Connectors
Power Automate connectors fall under four different tiers:
- Built-In Connectors: applications within the Microsoft Power Platform environment, data within the flow, and raw HTTP connections. These are always available to MM faculty and staff. Examples: HTTP, Power Apps, AI Builder.
- Standard Connectors: applications within the Microsoft 365 and Microsoft Dynamics environment, as well as third-party applications. These do not require additional licenses, but third-parties may impose fees for API access. Microsoft standard connectors are generally available to MM faculty and staff, but third-party connectors are typically blocked. Examples: SharePoint, Excel Online (Business), Office 365 Outlook, Power BI, RSS, Google Calendar, Dropbox, S/FTP, Twilio.
- Premium Connectors: applications published by Microsoft or third-parties that require an additional monthly or per-use license, and are denoted by a diamond icon (💎). These are generally blocked, but specific connectors may be allowed in the future depending on business needs and security, including HIPAA requirements. Examples: Microsoft Dataverse, SQL Server, Document AI, Adobe PDF Services, ServiceNow.
- Custom Connectors: internally-developed connectors that are not publicly available, and require the same license model as Premium Connectors. Blocked to all MM faculty and staff at the moment. Examples (prototyped by EFDC): MCommunity Groups, Freestyle Libre CGM Follower.
Allow/Block List
| Connector Name or Type |
Allowed? |
| Built-in Connectors |
✅ Yes |
| Standard Connectors Published by Microsoft |
|
|
Mail
|
â›” No*
* Will be disabled in Spring 2026 |
|
Outlook.com
|
â›” No |
|
Microsoft Teams Virtual Events (deprecated)
|
â›” No |
|
All other Microsoft Standard Connectors
|
✅ Yes |
| Standard Connectors Published by Third Parties |
â›” No |
| Premium Connectors |
â›” No |
| Custom Connectors |
â›” No |
Note that even if you are able to add a blocked connector to a flow, it will be blocked at run-time, causing the flow to fail.
Notes
- Although an effort was made to ensure this information is up-to-date and accurate, HITS may make changes from time to time. If unsure, open a help ticket (administrative support or data concierge).
Resources
About the Author
 |
Gabriel Mongefranco is a Mobile Data Architect at the University of Michigan's Eisenberg Family Depression Center. Gabriel has over a decade of experience with automation, data analytics, database architecture, dashboard design, software development, and technical writing. He supports U-M researchers with data cleaning, data pipelines, automation and enterprise architecture for wearables and other mobile technologies.
| | |
|