Firewall and proxy configuration recommendations

The following AODocs products communicate with AODocs servers to execute actions requested by end users, such as importing files, opening Microsoft Office files and applying sharing permissions:

The table below lists the URLs that the Smartbar and UFO/AFO access from your Chrome browser. If your organization uses an HTTP proxy or other network filtering equipment, these URLs must not be blocked by the proxy for the Smartbar and UFO/AFO to work correctly.

Notes: Where there are two URLs indicated, make sure you use the correct URL according to whether you're on a Google domain or a Microsoft tenant and according to the AODocs instance you're using. Learn more: Find out which AODocs instance you're using.




You're recommended to allowlist the entire domain as indicated, because the list of URLs may grow in the future.

Currently the list is:

to authenticate the user and grant OAuth2 authorization

to access to the AODocs installation page

to use Smartbar features such as library configuration or workflow tasks

to use the Gmail email conversion feature*
(US instance) 

(EU instance)

To access the AODocs interface and for all the AODocs API requests*

To use the Edit in Office feature for files not managed by AODocs

The Smartbar extension accesses this URL to get some configuration files*
(US instance) 

(EU instance)


To authenticate the user and grant OAuth2 authorization*
(Google domain)

(Microsoft tenant)*
Note: This isn't needed for Microsoft users.

For all Google API requests*
(UFO V6.0 and below)*
(UFO V6.1 and above)*

The UFO/AFO client accesses these URLs to get automatic updates


Was this article helpful? 5 out of 7 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request



Please sign in to leave a comment.