Prepare data and access safely
Want more background?
The idea in everyday life
Clean the fields, permissions, service accounts, and test environment needed for reliable connections.
Most automation failures begin before the first action—with inconsistent data or excessive access.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Keep an untouched pack and open test-cases.csv in a text editor. Use its exact header; the small format has eight unquoted comma-separated fields and no embedded commas/newlines.
- 2
Write the access matrix: operator reads CSV/config; runner writes the local in-memory queue and a downloaded export; Practice coordinator reviews holds/alerts; no external account or credential exists.
- 3
Keep exports in the project folder with a retention note. The runner does not autosave: export before closing, then restore the latest JSON on reopening.
- 4
Compare all six supplied records with the field dictionary; retain intentionally missing/duplicate/outage cases as tests, rather than cleaning away the conditions under test.
See how it works.
The supplied pack has T01–T06, config-reference.json, an expected result table and a simulated week-one.csv. Only fictional input is used. Restoring a run restores its existing destination IDs, which prevents repeated successful records from writing twice.
Did you cover these?
- Your work includes a clean field sample, access matrix, data-handling note, and reusable test dataset.
- Check this common mistake: Granting administrator access because it is faster than identifying the exact read and write permissions the workflow needs.
- Every connection, field, destination, retention period, and test record has an owner and justified purpose.
What to finish
A clean field sample, access matrix, data-handling note, and reusable test dataset.
Watch for this
Granting administrator access because it is faster than identifying the exact read and write permissions the workflow needs.
How can I tell I understand it?
Every connection, field, destination, retention period, and test record has an owner and justified purpose.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
Power Automate Tutorials
From Microsoft Power Automate. Watch here or open it on YouTube .
Watch for an idea you can use in the practice below. You can pause or skip this optional overview.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.