Using TenantID rather then default domain #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rather then use the default domain, which in my case most older customers are set to onmicrosoft.com domains for some reason. Why not create an API Asset Layout and give the Asset the name of the Microsoft Tenant.
This has the benefit of not monitoring the onmicorsoft.com domain if you aren't interested in it, and allows you to store the TenantID for all kinds of other endpoints such as Sophos, Fortinet, and pretty much anywhere you need to connect too.
You then just search for the tenantID rather then default domain.