Quick answer
A fair skills trial for a Microsoft 365 support candidate uses a sandbox tenant containing only test data, observable tasks with a stated expected outcome, and scoring criteria set before the trial. Use the same tasks and criteria for every candidate, record evidence as they work, and have a named reviewer check the record.
- Confirm no customer information is reachable from the sandbox, and document how access is removed afterwards.
- Check each task against current Microsoft documentation, and avoid trick questions or tasks needing your internal tools.
- Treat the trial as evidence of how someone works on defined tasks, alongside references and other checks.
A fair skills trial for a Microsoft 365 support candidate uses a sandbox with no production customer data. This article shows how to build a safe test environment, choose observable tasks and set assessment criteria. It is written for international it providers and technical leads and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A support candidate needs a fair skills trial using a sandbox with no production customer data.
What happens. A provider wants to assess a Microsoft 365 support candidate. It builds a test tenant containing only test users and test data, writes three tasks with the observation it expects for each, sets scoring criteria before the trial and records what the candidate did. The same trial is used for every candidate.
Safe test environment
Use a sandbox tenant or a test environment that contains only test data, and confirm that no customer information is reachable from it. Use the safety boundary field. A candidate should never see production data during a trial, and a mistake in the sandbox should cost nothing. Document who set it up and how access is removed afterwards.
Observable tasks
Choose tasks whose outcome you can observe, such as diagnosing a described mailbox access fault and stating the likely cause and next step. Use the task and expected observation fields. Check each task against current Microsoft documentation, because menus and features change. Avoid trick questions and tasks that depend on knowledge of your internal tools.
Assessment criteria
Set scoring criteria before the trial and record evidence as the candidate works. Use the scoring criterion, evidence and reviewer fields. Use the same criteria and tasks for every candidate so the comparison is fair. Decide beforehand what counts as meeting the standard, and who reviews the record. A trial shows how someone works on defined tasks; it does not replace references or other checks.
Candidate assessment worksheet
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Task | Expected observation | Safety boundary | Scoring criterion | Evidence | Reviewer |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Task | Expected observation | Safety boundary | Scoring criterion | Evidence | Reviewer |
|---|---|---|---|---|---|
| Diagnose a mailbox access fault (test tenant) | Candidate identifies the likely cause and next step | Test tenant only | Meets, partly meets, does not meet | Notes and screen recording if agreed | Technical lead |
Working through the completed row
In the row, the task is to diagnose a mailbox access fault in the test tenant. The expected observation is that the candidate states the likely cause and next step, the safety boundary is the test tenant only, scoring is meets, partly meets or does not meet, evidence is notes and the technical lead reviews.
Common mistakes
- Using production data.
- Changing criteria between candidates.
- Choosing trick tasks.
Questions to settle before you rely on it
- What test environment will you use?
- What does a good answer look like?
- Who reviews results?
How you know it is complete
The worksheet is complete when each task has an observation, boundary, criterion, evidence and reviewer. Record who reviewed it and the date.
Where you may not have the answer
A candidate finds an access route you did not intend. Stop the trial, fix the sandbox and record what happened. The handoff, not a guess, is the correct next step.
Your next action
Write three tasks and the scoring criteria before inviting anyone.
Discuss this role, required skills, working hours and review responsibilities with Web Design Davao. Outsourced staffing arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Web Design Davao employs and manages its Davao-based staff, including HR administration and payroll, and provides them as an outsourced service to companies overseas. See how staff are managed and how staff are hired.
Frequently asked questions
Why use a sandbox tenant for a skills trial?
A candidate should never see production data during a trial, and a mistake in the sandbox should cost nothing. A test tenant with only test users and test data keeps customers safe and makes the trial the same for everyone.
What kinds of tasks should a Microsoft 365 trial include?
Choose tasks whose outcome you can observe, such as diagnosing a described mailbox access fault and stating the likely cause and next step. Write the expected observation for each task in advance, avoid trick questions, and check each task against current Microsoft documentation.
How do you keep a candidate comparison fair?
Set the scoring criteria before the trial, use the same tasks and criteria for every candidate and decide beforehand what counts as meeting the standard. Record evidence as the candidate works, and have a named reviewer such as the technical lead check it.