Microsoft Licensing for iPads in the Workplace

How to avoid Microsoft license compliance traps

News provided by

Jun 20, 2012, 01:00 ET

KIRKLAND, Wash., June 20, 2012 /PRNewswire/ -- Employees who use personal devices like the Apple iPad to access Microsoft software on corporate networks are probably not covered by their employer's existing Microsoft license portfolio. Bring your own device (BYOD) scenarios can trigger unanticipated and expensive licensing requirements for Microsoft server applications, Office suites, and the Windows client OS. It can also impact the qualified device count that must be reported under Enterprise Agreements (EAs).

According to Rob Horwitz, a Microsoft licensing expert at the independent research company Directions on Microsoft, "Many IT professionals are shocked to find out the extent to which BYOD licensing depends on architecture. Allow users to access the corporate network one way and your organization will be on the hook for hundreds of dollars per year for each iPad. Allow access another way and your organization might be completely covered by the licenses it already owns."

Horwitz will explain the rules surrounding iPad use and describe several different technical approaches that minimize the Microsoft licensing costs triggered when iPads and other personal devices access corporate networks during a live webinar followed by a Q&A period on Thursday, June 28th at 10:00 am. PT. To participate, register at: directionsonmicrosoft.com/byod

About Directions on Microsoft

Directions on Microsoft is an independent IT analyst firm focused exclusively on Microsoft technologies, roadmaps and licensing since 1992. Directions is best known for its Microsoft Enterprise Software Roadmaps and Microsoft Licensing Guides. Their two-day Microsoft Licensing Boot Camp teaches Microsoft customers how to effectively license Microsoft products such as Windows Server, Exchange, SharePoint, SQL Server, and Office as well as maximize the ROI on their Microsoft Enterprise and Select agreements.

Contact: [email protected]

SOURCE Directions on Microsoft