Forum Discussion
NimbostratusOffice 365 not Working on APM proxy
Office 365 not Working on APM proxy.
We have created network access profiles, under network setting we provide client proxy and using PAC file.
We are seeing issue with our users when they connect through the VPN and access their mails thru their outlook via the Office 365. Our Office 365 traffic is routed thru proxy and firewall, the traffic is define thru the pac file. No issues encountered when accessing our email thru our corporate network only when they VPN and access their emails.
Here is the client settings “Advanced” configured on our APM.
Client Proxy Settings – Check Client Proxy Uses HTTP for Proxy Autoconfig Script – Check Client Proxy Autoconfig Script – Configured to point on our pac file Client Proxy Address – Blank Client Proxy Port – 80
I have also open my browser and point it to http://127.0.0.1:44777 and view what the pac file has in it and it giving me the correct file. Let me know if you need more information. Thanks.
Since the setup not working since begining, we have captured the data could see client sending syn and no syn ack/response from f5 APM. So whenevr the we use ACL to ( any any allow), outlook was connecting fine. Since we dont want to use any any ACL in the policy, we want to allow specific domain to allow related office 365, https://support.content.office.net/en-us/static/O365IPAddresses.xml. Since so many URLs mentioned in the aticle, please suggest best way to implement office 365 in APM proxy.
Martin_VlaskoAltocumulus
Hi Purna,
I was searching for why my browser is assigned with http://127.0.0.1:44777 as the Autoconfig script as there is not much documentation about it. And I found your this post of yours.
When you said that you configured the network access profile with "Configured to point on our pac file Client Proxy Address" - did you mean that in the field "Client Proxy Autoconfig Script" you entered the actual real IP address of your PAC file? (so something else than 127.0.0.1:44777?)
I am just trying to understand why does the client receive http://127.0.0.1:44777 as the autoconfig script address - is it some kind of F5 way how to proxy the proxy PAC file?
- boneyard
MVP
a seperate question might have been a better idea. but anyway yes, it seems APM uses that to serve a proxied pac file which you configure in the network access profile.
also see: https://support.f5.com/csp/article/K15130
as with many APM things documentation is quite limited, so if you have specific questions ask them and perhaps someone knows. or use f5 support.
- Martin_Vlasko
Thanks for reply boneyard. I asked here because the original question was in the same context as my issue and it seems that nobody else ever dealt with this topic on devcentral.
Thanks for the link, I have seen it before too, but it does not confirm it explicitly, hence I asked. But now I also think that it must be the case, APM setting this PAC file link in User's settings to proxy the actual PAC file.
