Cloud Discovery - Azure Gov and Commerical Tenants, Subscription Issues

[Morgan2]

Hi All,

Hoping you can help me figure this out. We recently migrated (finally) to patterns for cloud discovery, and with this we setup schedules for both our Gov tenant and our Commercial tenant. We have regional MID clusters. My issue is that the Gov tenant requires MID server properties to be set to grab the subscriptions correctly (https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/cloud-management-...). However, in setting these properties on the MID servers, it seems to interfere with the commercial tenant and the ability to pull subscriptions. When we try and pull the subscriptions, we get an error "

Discovery Subscription Error : Failed to execute API - Fetching token failed, status code: 400, response body: {"error":"invalid_request","error_description":"AADSTS90038: Tenant '#####' request is being redirected to the National Cloud 'MicrosoftOnline.COM". It seems to pick a random MID server to do this, which causes issues because the Gov side needs them but the Commercial side can't have them. Am I missing some property or something that can force it to use a specific MID server for each of these? Or some other non random way? Otherwise I'd have to have some of the MIDs have the properties and others not and hope when they try and grab their respective subscriptions, they hit one they can use.

I hope this makes sense. Appreciate any help I can get.

Thanks!

[Niklas Peterson · Accepted solution]

Hi,

Since the government tenant requires MID server properties that are different then you will need separate MID servers for the different tenants. When scheduling the Cloud Discovery you do it per Service Account so just set up schedules with a MID Server that matches the tenant and you should be fine. If you use MID server clusters then all the MID servers in the cluster needs the same properties.

Regards,
Niklas

[Morgan2]

Thanks Niklas, 

This is correct. I created a case with SN and they said the same. I find it rather annoying to need separate MID servers for the different tenants. There should be code to know when to use the MID properties and when not to. Regardless, it works in our case since we are using different clusters to scan the different tenants anyway. One other note from SN is to use the Cloud Operations Workspace for cloud discovery....in case anyone else can use the information.

Thanks!