Rolling out an agreed personal-device policy
Pilot an agreed BYOD arrangement with clear privacy boundaries, supported devices, business calling and tested removal of managed work information.

A personal-device policy needs a usable implementation. Staff should understand what they can do, what the business can manage and how support works before connecting their own phone or computer.
Start with an arrangement that’s been through your privacy and employment review. A signed policy on its own may not give you the right to monitor, inspect or erase personal information.
Explain what the controls do
Describe which device details administrators can see, which settings they can change and what happens when work access is removed. Base the explanation on the platform you’ve chosen, and check it on a pilot device.
Distinguish whole-device management from protection applied to particular apps. Microsoft’s Intune app protection overview describes controls for supported apps and work contexts. Confirm the operating system, app and account combinations in your pilot.
Offer another way to do the work when someone can’t or won’t use a personal device. Record support and expense arrangements alongside technical requirements.
Settle compensation before launch
Staff will ask what the business pays toward a phone they bought and a plan they pay for. Decide before launch, and write the answer into the policy. How you pay changes the tax treatment, according to the CRA’s cell phone and internet services guidance:
- An allowance for cell phone or internet service is always a taxable benefit.
- Reimbursing an employee’s service plan isn’t taxable if they’re required to use it for work, the plan has a reasonable fixed cost, and personal use doesn’t push the bill above the plan cost. Keep records that show why the plan is reasonable for the job.
- Reimbursing the cost of the phone itself is a taxable benefit, even if it was lost or damaged at work.
- For home internet you reimburse, the business-use portion isn’t taxable and the personal-use portion is.
Check the arrangement with your accountant or payroll provider before you announce it.
Pilot a small set of tasks
Try email, the files staff need and the business calling application if you use one. Test on the kinds of phones and computers staff will use, since they don’t behave alike.
Check update requirements and what the user sees when a device or app no longer meets the rules. Provide a recovery route that doesn’t depend on access to the blocked work account.
For business calls, verify the displayed number, voicemail and off-hours settings. With a calling app installed, some calls may still go out from the personal number, and emergency-call location may not be handled automatically. Check both.
Decide where work records can live
Decide which records may be stored offline and whether they can be copied to other apps. Test the restrictions, including exports and attachments.
Don’t back up an entire personal device into a business system just to capture a few work files. Check what’s collected and backed up against the privacy arrangement you agreed.
Explain what to report if the device is lost or an app behaves unexpectedly. Give staff a contact route from another device.
Test departure and removal
Microsoft’s selective app wipe guidance covers removing managed company data from supported apps. After sending the request, check that the removal finished. It won’t retrieve copies someone exported elsewhere.
Practise the process on test accounts and check the result. Confirm business records are preserved before you remove anything, and document any limits or exceptions.
On someone’s last day, removing the device isn’t enough on its own. In the Microsoft 365 admin centre, an admin can go to Users > Active users, reset the person’s password and select Sign out of all sessions. Microsoft’s steps note that sign-out can take up to an hour. A wipe also needs the device to connect to the internet before it runs, so a phone left switched off keeps what’s stored on it until then.
If customers reach staff through a business number in a calling app, reassign that number and its voicemail to the person taking over the work. A number that belongs to the employee leaves with them, so let regular customers know who to call.
Keep the policy current
Put a date and an owner on the policy, and review it at least once a year. Review it sooner when something changes: a new minimum operating system version, a new work app, a change of calling provider or a change in what you monitor. Tell staff what changed and why.
In Ontario, an employer with 25 or more employees on January 1 must have a written policy on electronic monitoring in place before March 1 that year. Ontario’s guide to the requirement says the policy has to state whether you monitor employees electronically and, if you do, how, in what circumstances and for what purposes. It also covers monitoring through an employee’s own computer used for work. Staff must get a copy within 30 days of any change, so update it alongside the BYOD policy.
Our managed IT services can help scope device and app controls around those agreed boundaries.


