From BYOD to UYOD

Bronze Contributor

We are experiencing transition from Bring Your Own Device (BYOD) to Use Your Own Device (UYOD) and we need to consider new requirements in this case. In case of UYOD, it is user’s personal PC and they have their own private data and information there and they might not want administrator to manage them or force to use Azure Account or connect to Domain , but due to sensitivity of jobs we need to use techniques and method to make sure they are staying safe and while we respect them using their own PC, we protect our cooperate data, so here are some best practices:

 

Manage Application User Account Not Windows Account: You could set policies in application level, for example if user connect to SharePoint online, we could set policy on what resources they have access to and what they don’t have and what is their access level.

 

Protect Your Company Data: You could use Microsoft Azure RMS or any other Data Protection service to protect sensitive data and even if they copy those data and move them around and try to share them because Azure RMS has been enforced , you are sure data won’t be leaked.

 

Be Website Oriented: We are leaving in era of Web Application, you could open Word, Excel, PowerPoint on web browser, you could encourage your users to use their browser to access company resources without installing any app. If they want app like experience, they could use cool new feature in Microsoft Edge where they could install website as application and feels like they install something but actually it is website.

 

In UYOD , users might not want to be managed by company because it is their own personal device and it is their home environment , in the other hand company might not be able to give them additional device and they might not be able to get one quickly. However they still want to work with their own device to get their jobs done. In this case, we need new management style and it is managing and controlling users and data on untrusted and unmanage device for long time. 

0 Replies