Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I'm encountering an issue setting up a Vnet datagateway. When trying to save the setup for a Vnet datagateway, I'm unable to save. The button in grayed out.
- Subnet is delegated to power platform (resource providers are approved)
- Subnet is bound to a NSG and RT. NSG is set open for internet access (routes throught AGW)
- user logged in is a Fabric administrator. It has a fabric trial licence
- Fabric F2 capacity is asigned
Anyone any suggestions?
Solved! Go to Solution.
Hi @JesseBR
You're encountering an issue where the Save button is grayed out while setting up a VNet Data Gateway in Microsoft Fabric, despite having followed the necessary setup steps. You've correctly delegated the subnet to Microsoft.PowerPlatform, ensured that the required resource providers are registered, and confirmed that the subnet is bound to an NSG and route table with internet access routed through an Application Gateway (AGW). Additionally, the logged-in user is a Fabric administrator with a Fabric trial license, and the F2 capacity is assigned. However, the grayed-out Save button typically indicates that something is either misconfigured or incomplete behind the scenes. One possibility is that the subnet delegation or configuration has subtle issues—for instance, having multiple or conflicting delegations, or incomplete network setup, which can prevent the portal from recognizing it as ready. Another potential cause is region mismatches between the subnet, resource group, and Fabric capacity, which are required to be in the same Azure region for the deployment to proceed. It's also worth verifying that outbound network traffic required by the Data Gateway is not being blocked or misrouted by the NSG or AGW—especially traffic to Microsoft endpoints like *.powerplatform.microsoft.com. Lastly, this issue can sometimes be due to frontend glitches in the portal UI itself, so trying a different browser or using an incognito window may help. If the issue persists, reviewing tenant-level policy restrictions or re-creating the setup with a clean subnet may be necessary to unblock the configuration
Hi, It suddenly worked. So I was still busy debugging... We can't find out why it started working. I think it must be due to front end glitchtes.
Hi @JesseBR,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @JesseBR,
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @JesseBR
You're encountering an issue where the Save button is grayed out while setting up a VNet Data Gateway in Microsoft Fabric, despite having followed the necessary setup steps. You've correctly delegated the subnet to Microsoft.PowerPlatform, ensured that the required resource providers are registered, and confirmed that the subnet is bound to an NSG and route table with internet access routed through an Application Gateway (AGW). Additionally, the logged-in user is a Fabric administrator with a Fabric trial license, and the F2 capacity is assigned. However, the grayed-out Save button typically indicates that something is either misconfigured or incomplete behind the scenes. One possibility is that the subnet delegation or configuration has subtle issues—for instance, having multiple or conflicting delegations, or incomplete network setup, which can prevent the portal from recognizing it as ready. Another potential cause is region mismatches between the subnet, resource group, and Fabric capacity, which are required to be in the same Azure region for the deployment to proceed. It's also worth verifying that outbound network traffic required by the Data Gateway is not being blocked or misrouted by the NSG or AGW—especially traffic to Microsoft endpoints like *.powerplatform.microsoft.com. Lastly, this issue can sometimes be due to frontend glitches in the portal UI itself, so trying a different browser or using an incognito window may help. If the issue persists, reviewing tenant-level policy restrictions or re-creating the setup with a clean subnet may be necessary to unblock the configuration
Hi @JesseBR Ensure the subnet is delegated to Microsoft.PowerPlatform/vNet only and that NSG rules allow required traffic. Verify RT doesn’t block gateway communication and that Fabric F2 capacity is active. Check that the user has admin permissions and an active Fabric trial license. If issues persist, revalidate all configurations.
Hi @JesseBR,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Here are some steps to troubleshoot to resolve the issue:
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi @JesseBR,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.
Thank you.
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |