I will most likely start locking this down harder by removing some of the directories I've setup with app proxy and see what it breaks. ews/ - Again, not sure what this helps with regards to remote clients. powershell/ - Not sure what functionality is provided there for remote clients and I may disable this I have also setup app proxy with the following directories I'm not sure if any other issues will be encountered because of the /rpc directory. What this means is that my mobile clients will not ask me to sign in via Office 365 Hybrid Modern Authentication and instead asks me for a password in the app. A Web exception occurred because an HTTP 503 - 503 response was received from Unknown. Testing HTTP Authentication Methods for URL Opens a new window. So my assumption is that because I'm using Azure App Proxy to access the /rpc directory which is another proxy, something breaks down, because my exchange connecticity analyzer tests seem to fail on that step. Outlook anywhere, I believe, uses the /rpc directory under Exchange and from what I'm gathering, the /rpc directory does a proxy type of service. What I have found though, is that Outlook Anywhere does not seem to work. Opens a new window - Allow Back End Exchange Control Panel Opens a new window - Allows web based email Opens a new window - Allows Mobile Devices (non rich clients) to connect and syncįor the remote users that use web based email Opens a new window - Allows Outlook (Rich Clients) to connect and sync Opens a new window - Allows initial autoconfiguration to begin The ones for my remote users using outlook and mobile clients are What I found is that I have to create an app proxy for several exchange directories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |