Workspace ONE Access Horizon Args

I had an interesting customer use case last week that called for some ingenuity with how we establish Horizon app launch URIs in Workspace ONE Access. In short, a 3rd party agency required management access to retail location IoT devices on a closed network. These contractors were road warriors of sorts; sometimes onsite, but more often than not, out in the field servicing other customers of their own. We call this the “managed aisle” use case in my world, referencing a common retail arrangement where 3rd party vendors manage certain retail product aisles in a store (i.e. beverages). The customer was already using Workspace ONE as the unified app catalog for their enterprise and third party MSPs, publishing an assortment of management and enterprise tools that could only be accessed when on the intranet. They also had an existing Horizon RDS farm deployed with the same management suite for badged resources to perform similar functions on company-owned equipment. So the question became, how could we breadcrumb the user experience in such a way that a contractor could continue consuming applications […]