cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bmaudlin
Level 8 Champion
Level 8 Champion

O365 connector connectivity query

Hi Guys,

I am looking to implement the new O365 connector to draw down licensing and usage information. 

However I'm unable to find it documented what Microsoft IP ranges should be open to allow this connectivity.

Any advice would be appreciated. 

Ben

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.

5 Replies
mag00_75
Level 8 Champion
Level 8 Champion

Hi

We are using the connector together with proxy setting. The following URLs was opened

https://login.microsoftonline.com/common/oauth2
Https://graph.microsoft.com
Https://reports.office.com
Https://reportsweu.office.com

I do not recommend open up all IP-adresses since they are many and changes over time

Hi @bmaudlin ,

I've done the integration with O365 in a FNMS cloud setup and we need to have internet connectivity to the Beacon and the URL's suggested by @mag00_75  should be accessible. Later to get the data from the cloud we have to have a user with cloud app administrator Privileges for the  O365 Azure Tenant from which we have to import the data. There are 2 methods and attached the document for reference and hope it helps.

We need the below from the Azure administrator before starting.

1. OAuth 2.0 authorization endpoint (v2) URL

2. OAuth 2.0 token endpoint (v2)

3. Application Client ID

4. Redirect URL

Regards

Thanks guys for the update.

I'll take note of those steps provided, my only outstanding issue is, we can only whitelist on IP ranges rather than URL's so I'll see if I can track down these IP ranges on the suggested URL's

Ben

Hi @bmaudlin 

Microsoft has published some documentation in regards to their IP adresses. Hope you will find this page helpful.

https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges

 

I think the new connector doesn't require admin privileges anymore. The old connector did, which our security team didn't like.
Erick Hacking, CSAM, CHAMP
IT Software Asset Manager, Lead Sr.
0 Kudos