Updateable Objects

[lullejd]

Hi all,

Is anyone using updateable objects in R80.20? I am trying to use them for office 365, however i don't think they work as they should.

Basically what i need to do is just give access to internet for a specific client to only office 365. My reasoning is to create an access rule as below:

Rule 1

Source - PC

Destination - Updateable Objects Office 365

Port any

Action - ALLOW

Rule 2

Source - PC

Destination - Any

Port - Any

Action - BLOCKED

The PC is excluded from HTTPS inspection.

The PC is able to reach office 365, manage to login, however after login a blank page is displayed.

Anyone experiencing such issues?

Thanks in advance 🙂

[G_W_Albrecht]

I expect that you know sk131852: Updatable Objects in R80.20 and above and thru that, also Unexpected drops on the Security Gateway while using Updatable Objects: refer to sk121877. Further information can be found in sk135572: Microsoft Office 365objects as Network Objects in R80.20 and sk122636: How to troubleshoot Updatable Objects in R80.20 and higher.

[lullejd]

Hi Albrecht,

Thanks for your reply.

All those SKs were followed accordingly. That's why i was asking because it is not clear on what might the issue be. The objects are updating successfully on the gateways.

To be honest, i opened a TAC case and their reply was to give them all of the IP addresses which are being blocked from tracker and allow accordingly. Which for me I don't see this as a solution as this defeats the whole scope of having Office365 updateable objects.

[Tal_Paz-Fridman]

Hi

It could be that after the initial login the page is redirected to other pages in *.microsoft.com or *.office.com.

Try using the log generated to determine the exact domains and add them manually to the rule with the Updatabale Object

HTH

Tal