CloudReady uniquely and out-of-the-box supports testing OWA when accessed from a federated (SSO) or managed account. Using CloudReady OWA Sensors for End-to-End Outlook Web App MonitoringĮxoprise CloudReady has long supported monitoring OWA from our Private Sites (behind the firewall) and from public clouds – wherever you have users that are accessing OWA. Even more-so for the occasional user or remote disaster recovery use-case of Outlook Web App. Understanding the interaction of SSO, proxies and OWA and how they are performing, continuously and from the users perspective, is paramount to ensuring performance, uptime and SLAs are met. When enterprises provide support for connecting to Exchange or Office 365 through OWA, its usually integrated with a Single Sign-On (SSO) login solutions such as Okta, Ping, or more frequently Azure AD and Active Directory Federation Services (ADFS). Another use case we see is leveraging OWA for Disaster Recover (DR) or emergency access. For manufacturing or retail, OWA is easy to use and setup for occasional users who may only need quick email or calendar access from Exchange. Another use-case we see from customers is shared desktops, terminals or kiosks. While the thick-client Outlook (2016, 2013, and earlier) is frequently used to connect to Exchange and Office 365, Outlook Web App is easy to use in a pinch when you are remote. Outlook Web App Login How to Monitor Outlook Web App Login and Why Its Important If you are looking to test the OWA 365 Login then Exoprise has the tools to do so. OWA is the professional web-based client for accessing all of the greatness of Exchange from any web-browser. This is not to be confused with name changing free hosted email product from Microsoft. See this Wikipedia entry for the full geeky history. Outlook Web App (OWA) has had many names over the years from Exchange Web Connect (circa 1995) to the now (somewhat agreed to) Outlook Web App.
0 kommentar(er)
