Power Platform Development

Printer backup files in .dcm and .abk formats were consistently being blocked by the firewall, and a zero-trust policy meant whitelisting by file type wasn't an option. Adam built a two-flow system to solve this: a technician fills out a Preflight Form with the order number and client email, which automatically creates a dedicated SharePoint folder for that order and generates a secure upload link. The link itself encodes the order number, recipient, and a 14-day expiration directly into a Base64-encoded string — nothing is exposed to the client, and the link self-expires without needing a database lookup. The client receives a simple one-button upload form by email, and when they submit a file, the second flow decodes the embedded parameters, validates the expiration, and routes the file into the correct SharePoint folder automatically. This eliminated firewall blocks entirely, gave technicians a centralized, organized history of every order's files, and significantly improved the client experience.

Before this system, users without any technical background would often walk up to IT directly rather than email, which created constant interruptions and made it harder to properly triage and document issues. Adam built a Power App ticketing form — deployed as a bookmarked link through Intune — with just three simple inputs: an issue type dropdown, a short description field, and an attachment option for screenshots. Submissions are logged directly to a SharePoint list, and a second flow picks up each new submission, compiles the details, and sends a properly formatted email to IT's ticketting system on the user's behalf. This gave less technical users a guided, low-friction way to submit issues, preserved proper ticket documentation and chain of communication, and served as a reliable fallback even when a user's email access was down. The issue type dropdown was also designed with scalability in mind — specific categories could be configured to trigger an automated response with a self-service guide for common issues like restarting a computer or clearing a printer queue, reducing ticket volume for IT on routine requests before a technician ever needs to get involved.

Built two parallel flows that query Microsoft Graph weekly for non-compliant Windows and iOS devices enrolled in Intune. Each flow compiles the results — including serial number, last check-in time, and the associated user principal name — into a CSV report and emails it directly to IT. The flows were intentionally designed to be extended further, with the underlying structure able to support automated remediation actions such as triggering a remote Intune sync on the affected device or notifying the device owner's manager directly, rather than relying purely on manual IT follow-up.

A weekly flow that reads all Entra ID groups, compares the current state against a stored baseline in SharePoint, and logs any additions, deletions, or modifications. When changes are detected, an email summarizing exactly what changed is sent to IT, and the baseline is automatically updated to reflect the new state for the next comparison. This closed a visibility gap where group membership changes — potentially indicating unauthorized access or misconfiguration — previously went completely undetected.