recently I have received many questions in regards to bypassing Office 365 traffic based on the new Microsoft categorization as "Allow", "Default" and "Optimize", which we have not yet taken into account before.
According to my (limited) understanding this categorization should be seen as
- "Optimize": Do not touch this traffic at all - "Allow": Do not block or modify this traffic - "Default": You can filter this traffic
In the past we only used the "Required" attribute and the "by product" categorization we always had. So utilize the additional categorization I have created a few more lists and a rule set, which basically categorizes the traffic into "Optimize", "Allow" and "Default" by using user-defined properties.
The rule set by default will allow you to simply Bypass/Not Bypass the traffic based on categorization, but along with the user-defined properties it would be possible to even build more complex rules like "Bypass Allow Traffic for Exchange Only".
I would like to
1.) Share the rule set with you 2.) Collect feedback on how you bypass Office 365, so the rule set can grow and find its way into the product
If anyone is willing to try this out and help me with some details on how Office 365 traffic is treated in your company, please reach out to me. I am willing to learn about potential use cases and what changes our existing Office 365 rule set may need along with the categorization of traffic to make it useful, understandable and easy to manage for customers.
would using Enable HTTP.Tunnel instead of Stop Cycle make sense? This should pass the response as-is effectively bypassing the response cycle completely, save some cpu cycles and make sure the office 365 traffic will never produce an error in the rule engine.
I am not sure why we have decided in the past to go with Stop Cycle. Maybe due to logging, I think if we use the tunnel event we may even miss some basic details like transferred bytes in the logging.
So far it works good, I have not seen any complaints about using the Stop Cycle action. I think using tunnel event might save some CPU cycles but I also believe that - compared to what other things MWG has to perform - it won't have much of an impact.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.