How to configure the Microsoft and Office 365 connectors to connect to the Internet through a proxy or firewall

How to configure the Microsoft and Office 365 connectors to connect to the Internet through a proxy or firewall

Summary

This article describes the following information related to the Microsoft 365 and Office 365 (deprecated) FlexNet Manager Suite connectors:

  • How to configure proxy details that are used to connect to the Internet.
  • What Internet sites (URLs) the connectors must be able to access.

Configuring proxy server details

For FlexNet Manager Suite 2018 R2 (13.1.x) and newer beacon versions:

Use the Proxy Settings section in the Create PowerShell Source Connection FlexNet Beacon dialog to enter proxy server, username and password information.

For FlexNet Manager Suite 2018 R1 (13.0.x) and earlier beacon versions:

The Microsoft 365 and Office 365 (deprecated) connectors use the proxy configuration for whichever user account runs ComplianceReader.exe process that makes a connection to Microsoft or Office 365 APIs.

This process is commonly executed by the service account used for the FlexNet Beacon Engine Windows service. The proxy details configured in the Windows profile for that user will be used when connecting to these connectors.

Proxy settings may be set for all users through Active Directory Group Policy or another similar mechanism. This would typically be required if the service is configured to run as the Local System account (the default) or a non-interactive named account.

If the service is configured to run as a interactive named account, proxy details may also be configured interactively. Launch Internet Options as that user from Internet Explorer's Tools Menu or from the Control Panel. Enter the proxy settings needed to be able to go online and access Microsoft or Office 365 APIs:

ChrisG_0-1622432440847.png
 

Additional information: Running the Beacon Engine Service using a named user account

The FlexNet Beacon Engine service is configured to run as the Local System account by default. This can be changed to run as a named user account with local administrator rights on the beacon. Be aware that this configuration will likely be lost and need to be manually reapplied whenever the beacon component is upgraded or reinstalled.

Internet URLs accessed by the connectors

The following Microsoft article details URLs and IP address ranges used by APIs that the connector uses to retrieve data from the Microsoft 365 and Office 365 Cloud environment: Office 365 URLs and IP address ranges

Also be aware of the following practice detailed on the Microsoft article:

Endpoints data is updated as needed at the beginning of each month with new IP Addresses and URLs published 30 days in advance of being active. This allows for customers who do not yet have automated updates to complete their processes before new connectivity is required.

While the information in that article should be considered as definitive, a summary of some key URLs which may be used during the connector operations are noted below.

Microsoft 365 connector

The beacon will require at minimum the access to the below URLs for the initial connection to Microsoft 365:

To gain the full functionality of the Microsoft 365 connector the connector will require access to all the URLs and IPs contained in the following website.

Office 365 (deprecated) connector

The beacon will require at minimum the access to the below URLs for the initial connection to Office 365:

 

Labels (2)
Was this article helpful? Yes No
No ratings
Comments

Hi @GregBirk ,

does this mean, that the proxy setting in the Beacon O365 setup has no effect and it must be a local beacon setting?

2019-11-26 14_35_07-VW_SAM - VMware Workstation.png

hi @dennis_reinhardt 

i too agree with you on this and we can use the Adapter in the Flexnet Beacon suite to configure the same i did integrate office 365 but not via proxy.

Regards, 

varma

Hi @dennis_reinhardt  and @winvarma.  Based on your questions, I have updated the article to include the Important note that appears in the Summary section of the article. 

Version history
Revision #:
9 of 9
Last update:
‎May 30, 2021 11:02 PM
Updated by: