MCAS APIs works even without portal and region name in URL's subdomain

%3CLINGO-SUB%20id%3D%22lingo-sub-1486081%22%20slang%3D%22en-US%22%3EMCAS%20APIs%20works%20even%20without%20portal%20and%20region%20name%20in%20URL's%20subdomain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1486081%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20using%20Microsoft%20Cloud%20Application%20security%20to%20perform%20the%20application%20discovery%20on%20the%20traffic%20logs%20which%20I've%20ingested%2Fuploaded.%20I'm%20using%20the%20REST%20APIs%20to%20upload%20my%20log%20files%20to%20the%20platform.%20Here%20is%20the%20reference%20from%20which%20I've%20written%20my%20script%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fcloud-app-security%2Fapi-introduction%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fcloud-app-security%2Fapi-introduction%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20as%20mentioned%20in%20the%20above%20documentation%2C%20we%20need%20to%20create%20the%20API%20URL%20from%20the%20full%20URL%20which%20includes%20the%20tenant%20name%20and%20region%20name%20followed%20by%20%22portal.cloudappsecurity.com%22%20followed%20by%20%22%2Fapi%2Fv1%2F%3CENDPOINT%3E%22.%26nbsp%3B%3C%2FENDPOINT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20format%20is%20working%20fine%20but%20when%20I%20try%20my%20API%20call%20using%20just%26nbsp%3B%22portal.cloudappsecurity.com%22%20followed%20by%20%22%2Fapi%2Fv1%2F%3CENDPOINT%3E%22%2C%20It%20uploads%20my%20file%20on%20my%20portal%20correctly.%20So%20I%20think%20it's%20inferring%20my%20portal%20URL%20from%20the%20API%20token%20which%20I've%20provided%20correctly.%26nbsp%3B%3C%2FENDPOINT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20is%20this%20understanding%20correct%3F%20How%20can%20it%20correctly%20upload%20my%20logs%20in%20my%20tenant%3F%20Are%20there%20any%20consequences%20using%20the%20API%20URL%20without%20my%20tenant%20name%20and%20region%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20searching%20the%20same%20issue%20on%20the%20internet%20and%20docs%20but%20nothing%20is%20mentioned%20about%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1486081%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20App%20Security%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECloud%20Discovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

I'm using Microsoft Cloud Application security to perform the application discovery on the traffic logs which I've ingested/uploaded. I'm using the REST APIs to upload my log files to the platform. Here is the reference from which I've written my script: https://docs.microsoft.com/en-gb/cloud-app-security/api-introduction

 

Now, as mentioned in the above documentation, we need to create the API URL from the full URL which includes the tenant name and region name followed by "portal.cloudappsecurity.com" followed by "/api/v1/<endpoint>". 

 

This format is working fine but when I try my API call using just "portal.cloudappsecurity.com" followed by "/api/v1/<endpoint>", It uploads my file on my portal correctly. So I think it's inferring my portal URL from the API token which I've provided correctly. 

 

So is this understanding correct? How can it correctly upload my logs in my tenant? Are there any consequences using the API URL without my tenant name and region? 

 

I've tried searching the same issue on the internet and docs but nothing is mentioned about this.

 

Thanks!

 

0 Replies