Forum Discussion
Issue with gateway cmdlet Connect-DataGatewayServiceAccount
As final update, Microsoft has confirmed that the issue exists and the DataGateway cmdlet is not compatible with Az PowerShell cmdlet. The problem that I have described above does not get resolved by disconnecting Az Account using `Disconnect-AzAccount` or even removing the Az module using `Remove-Module -Name Az`.
Microsoft has responded that they are going to deploy a fix but it'll be after a month. Therefore I'm closing this thread now and give an update in another forum when there is a fix.
To ellaborate the issue further I've run the two scenarios below. The first screenshot is where I do not use Az module to get the service principal secrets.
This scenario is where connect to Azure account using `Connect-AzAccount` first and without reading the key vault secrets the `Connect-DataGatewayServiceAccount` command fails to connect to Power BI service.
Hi mzare,
Can you add the -Verbose parameter at the end of your Connect-DataGatewayServiceAccount line and see if that gives you more information?
Btw, what is the Az module version you are using? That would be useful to know to reproduce your issue.
Same error message with verbose option added. I'm using latest versions of Az and DataGateway as my solution runs on a vmss that gets redeployed every day with the latest version of the cmdlets.
I've also received this from microsoft support:
According to our documentation, the Connect-DataGatewayServiceAccount cmdlet appears to be incompatible with the Az module, but we are currently investigating internally to find any possibility.
Hi, mzare
Thank you for your detailed feedback and the efforts you have made to resolve this issue. I understand how frustrating it can be to encounter this persistent error.
Thank you for your patience and the steps taken to investigate this matter. As mentioned earlier, the Connect-DataGatewayServiceAccount cmdlet does not appear to be compatible with the Az module, and Microsoft Support is actively investigating this issue internally.
You can mark your response as a solution, which can help others facing similar issues and help improve our documentation and support.Thank you again for your cooperation and understanding.
Best regard
Ok, thanks for sharing that feedback from Microsoft Support. That is useful to know.