Registering on-premises data gateway failure: ADGraphGroupOperationFailed

Question

Hi, I am facing an error when I try to register on-premises data gateway. I followed all the documentation instructions and prerequisites. I also tried different regions, and different high-privileged user accounts, and different machines and firewall configurations. I am using Gateway version number: 3000.54.8 (August 2020)

Response status code does not indicate success: 500 (Internal Server Error)
Request Id: 82ad4776-3024-4619-9ba6-a2b208989bc2
Timestamp: 8/31/2020 5:11:45 PM +00:00
ErrorCode: ADGraphGroupOperationFailed

at Microsoft.PowerBI.DataMovement.ExternalClient.PowerBIDataMovementClientExtensions.<EnsureSuccessfulDMMSRequest>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.ExternalClient.PowerBIDataMovementClientExtensions.<CreateOrReplaceUnifiedGatewayAsync>d__2.MoveNext()

Answer 1

Hi AhmedTaha-3595,

I see that you are using onmicrosoft.com email ID while logging to OPDG.
In one of the prerequisites, it is mentioned that username@keyman .onmicrosoft.com will only work if you have Office 365 offering.

If you signed up for an Office 365 offering and didn't provide your work email address, your address might look like username@keyman .onmicrosoft.com. Your account is stored in an Azure AD tenant. In most cases, the User Principal Name (UPN) for your Azure account is the same as your email address.

Can you please search for Azure Active Directory and confirm whether your tenant is offering is Office 365. Search for "Azure Active Directory" and in the overview of Azure Active Directory you will see Licence details.

I was able to reproduce the issue if the tenant is not an Office 365 offering such as Azure AD Free etc.

Update:
If your tenant offering is Office 365 and still facing the issue then this is a known issue and the product team is working on this. Right now the ETA to deploy the fix is 9/13 and can be changed due to unavoidable situations. Will keep you posted once fixed.

Update 9/14:
The issue is fixed now and working as expected.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.