Forum Discussion
Issue with gateway cmdlet Connect-DataGatewayServiceAccount
- 1 year ago
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.
Thank you Expiscornovus and SaiTejaTalasila
Hi, mzare
If you can't find the corresponding cmdlet, you can import it into Powershell first:
Import-Module -Name DataGateway
Then run the following command:
Connect-DataGatewayServiceAccount -ApplicationId $secretClientId -ClientSecret $secretClientSecret -Tenant $secretTenantId
Of course, you can use Power Shell ISE to see if this module has been successfully installed on your computer. If it is installed and cannot be called directly, please import it first.
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- mzare1 year agoFrequent Visitor
The issue is not importing the module. The issue only occurs when I run the Az command below first. Otherwise everything works fine independently.
Connect-AzAccount -Identity
- Expiscornovus1 year agoMost Valuable Professional
Hi mzare,
Maybe it is confused about the Az session.
Have you tried adding the a line with Disconnect-AzAccount before the Gateway lines to see if that makes a difference?
Disconnect-AzAccount Install-Module -Name DataGateway -Confirm:$False -Force Connect-DataGatewayServiceAccount -ApplicationId $secretClientId -ClientSecret $secretClientSecret -Tenant $secretTenantId- mzare1 year agoFrequent Visitor
Yes, disconnecting doesn't help neither.