Forum Discussion
Helper VCreate Gateway Connection - API
Hi pvuppala
While PowerShell provides flexibility and encryption support, many teams are indeed exploring more scalable and automated solutions like Power Automate or Azure Automation to remove dependency on individual desktops.
As of now, Power Automate doesn’t natively support direct creation of gateway connections through built-in connectors, but you can integrate it with custom connectors or Azure Functions that call the Power BI REST API (like the createDatasource endpoint you referenced).
By doing so, you can fully automate the process using cloud-native tools and potentially trigger actions based on events (like password rotation alerts from CyberArk).
Long-term, combining Azure Key Vault for secrets management and an automation engine like Azure DevOps or Logic Apps could give you even more control and traceability, especially if you're aiming for CI/CD practices around Power BI deployments.
It’s promising to see more organizations moving in this direction, and Microsoft’s growing API surface will hopefully support these use cases more natively in the future.
Community SupportHi pvuppala ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
Thank you rohit1991 , for sharing the valuable information.
Hi pvuppala , In addition to rohit1991 response. i am adding some points.
Automation Alternatives to PowerShell on Desktops
1. Azure Automation + Runbooks
Headless automation of PowerShell scripts. Secure, cloud-based, scheduled or event-triggered. Supports linking to Azure Key Vault or CyberArk for credential management. Can be triggered from Power Automate, Azure DevOps, or any webhook/event.
2. Power Automate (Flow) + HTTP Actions
You can create a custom connector or use HTTP with Azure AD to call the Power BI REST API directly. You will need to register an Azure AD App with appropriate permissions (Tenant.Read.All, Dataset.ReadWrite.All). Acquire a token using Client Credentials Flow. Use HTTP or HTTP with Azure AD connector to call the API.
Note: Power Automate doesn't natively support encrypted credential handling like CyberArk. You'd need to call an external API that returns the credential securely.
3. Azure Functions (C# / PowerShell / Python)
Great for building small, API-triggered microservices. Your Azure Function can retrieve credentials from CyberArk using its REST API. Call Power BI Gateway API to create datasources. Be triggered by events (e.g. new dataset metadata, schedule). Secure execution and credential storage via Azure Key Vault or managed identity.
4. Azure DevOps Pipelines
If your environment is DevOps-centric, you can automate these tasks as part of a release pipeline. Secret variables or Key Vault can inject credentials. Run PowerShell or REST calls via agents.
For Handling Credentials (Password Rotation Support)
CyberArk Integration: Use CyberArk’s REST API to fetch credentials at runtime. Combine with Azure Function or PowerShell script to dynamically insert into the credentials body of the Create Datasource API.
Azure Key Vault: Supports automatic key/secret rotation when integrated with compatible services. Secure and scalable credential storage.
Please refer below Sample Architecture
Power Automate Flow (triggered by business need)
↓
HTTP Webhook or Azure Function (retrieves CyberArk creds)
↓
Power BI REST API (Create Gateway Datasource)
Note: Move away from desktop-based PowerShell to Azure-hosted automation. Fetch credentials at runtime securely (CyberArk or Key Vault). Wrap logic in reusable APIs (Functions or custom connectors). Plan for service principal-based auth (avoid user context where possible).
Please refer Microsoft articles and community threads.
Data Gateway : Automation using PowerShell - Part ... - Microsoft Fabric Community
Manage connections in Power Automate - Power Automate | Microsoft Learn
Learn to manage on-premises data gateways - Power Automate | Microsoft Learn
Solved: Automated Refresh of Power BI Dataset using Powers... - Microsoft Fabric Community
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you