That is correct in Internet Access profile normally the bypass policies are allowed and take precedence. In this scenario we would need to check if in the Bypass policies these endpoints are being bypassed or not. Only define the endpoints which you want to be bypassed and whose traffic you don't want to acquire.
First analyze the traffic when GReminders is accessed, keep note of the endpoints and the ports and then it would be required to cross check if they have defined to be bypassed.
Whether the traffic will be captured or not depends on what is defined in the default Internet Access policies i.e. in Custom Bypass, Default bypass and default acquire. Default acquire takes lowest precedence after all bypass rules are evaluated.
Traffic is evaluated from top to bottom, which means it only gets acquired by the Internet traffic profile if it’s not being bypassed in one of the bypass rules.
The changes made in Internet Access profile should be in harmony with Microsoft traffic profile. When you enable the Internet Access forwarding profile, you should also enable the Microsoft traffic forwarding profile for optimal routing of Microsoft traffic. You enable the Microsoft traffic profile by selecting the profile checkbox on the same page where you enable the Internet Access traffic forwarding profile.
When a rule is set to Bypass in the Microsoft traffic profile, the Internet Access traffic profile will not acquire this traffic. Even with the Internet Access profile enabled, the bypassed traffic will skip Global Secure Access acquisition and use that client's network routing path to egress to the Internet. Traffic available for acquisition in the Microsoft traffic profile can be only acquired in the Microsoft traffic profile.
So, if we're requiring any traffic to be acquired in Internet access then it should not be set to bypass in Microsoft traffic profile.