OVERVIEWCASE STUDIES

PROJECT NOTES / SELECTED WORK

Real systems.
Real-world constraints.

A selection of substantial engineering engagements, described through the problem, the work and the stage actually reached. Client organizations, colleagues, identifiers and sensitive configurations are omitted.

CASE STUDIES

What interests me most is the path from uncertainty to a supportable solution. Some examples below are delivered systems; others are pilots or discovery work. I have kept those distinctions visible.

See related tools & scripts ↗
01INTEGRATION / OPERATIONAL AUTOMATIONOperational workflow

A document transfer that needed to work for a year

A recurring third-party imaging/data export needed to reach a SharePoint document library reliably over an extended period—not simply be copied once.

The problem beneath the task

The hard part was not uploading a file. It was designing a workflow that could be monitored, recovered and handed over while dealing with changing network paths, remote endpoints and scheduled delivery.

Where it stands

The automation was completed and set to run on a twelve-month operational schedule. The case reinforced that monitoring, support ownership and predictable recovery are part of the product.

Explore the engineering approach
  1. Built a hosted administration and reporting layer around scheduled secure file transfers and cloud delivery.
  2. Used SFTP-oriented source retrieval and SharePoint/Microsoft Graph integration patterns, with scheduling and status visibility.
  3. Worked through connectivity restrictions, supported an alternate relay path and kept operational troubleshooting accessible.
  4. Focused on progress tracking, failure visibility, duplicate-handling considerations and long-term maintainability.
SharePoint OnlineMicrosoft GraphSFTPPHP / hosted portalScheduled jobs
Related tool or script
02IDENTITY / MOBILE SECURITYRolled out

Securing personal devices without losing the users

A bring-your-own-device rollout had to protect business data on personal iOS and Android phones while keeping mail, Teams, OneDrive and contacts usable.

The problem beneath the task

Policy compliance was only part of the challenge. Calendar access, contact synchronization, app prompts and the distinction between device compliance and app protection directly affected adoption.

Where it stands

The rollout progressed through pilot testing to enforcement. Follow-up support addressed application access and user experience—a reminder that successful security is also a change-management exercise.

Explore the engineering approach
  1. Configured and validated Microsoft Intune mobile application management and Conditional Access strategies.
  2. Tested policies with a pilot group before expanding enforcement and supported real post-rollout troubleshooting.
  3. Investigated Outlook contact synchronization, native calendar limitations and the effect of removing older mail configurations.
  4. Used policy inspection and scripted checks to compare the configured settings with the intended requirements.
Intune MAMConditional AccessiOS / AndroidOutlookPowerShell
Related tool or script
03MICROSOFT 365 / DEVICE SECURITYPilot preparation

Preparing an identity and endpoint security pilot

An organization needed an evidence-led path toward stronger authentication, endpoint compliance and encryption controls without disrupting shared workstations.

The problem beneath the task

Licensing, pilot selection, current authentication configuration, device visibility, hardware readiness and policy assignments all had to be understood before activation.

Where it stands

Discovery and pilot policies were prepared, but live device enrollment and end-to-end BitLocker validation were dependent on device readiness. It is a prepared pilot, not a claim of fleet-wide completion.

Explore the engineering approach
  1. Ran read-only Microsoft 365/Graph discovery covering licensing, identity, authentication, device enrollment, compliance and configuration.
  2. Prepared a scoped authentication approach and Windows compliance policy with BitLocker configuration and Entra recovery-key escrow requirements.
  3. Reviewed and corrected escrow-related policy properties while retaining an unassigned pilot configuration until devices were ready.
  4. Coordinated pilot sequencing around two designated workstations and their management-agent availability.
Entra IDIntuneBitLockerMFAMicrosoft Graph
Related tool or script
04EMAIL / IDENTITY THREAT DEFENSEConfigured / validated

Coordinating multi-domain security onboarding

A multi-domain Microsoft 365 environment needed consistent security-platform onboarding across a substantial user population.

The problem beneath the task

Security products, group membership, user eligibility and tenant authorization must line up; a console saying “connected” is not the same as validating the protection workflow.

Where it stands

Core integrations were configured and hundreds of eligible users were prepared or enrolled in security-awareness workflows; final administrative validation and handover activities were tracked separately.

Explore the engineering approach
  1. Prepared user inventories, group structures and import workflows spanning several email domains.
  2. Connected and validated cloud email security onboarding, including authorization, learning/monitoring scope and visible email activity.
  3. Checked identity-threat protection integration and security-awareness enrollment workflow state.
  4. Used reconciliation and post-deployment checks to distinguish prepared, configured and validated items.
Microsoft 365Email securityIdentity threat defensePowerShellUser provisioning
Related tool or script
05DATA / MIGRATION DESIGNDiscovery & design

Discovering the shape of a major file migration

A long-lived combination of file-server data, DFS paths, NAS storage and Microsoft 365 identities needed a clear destination strategy.

The problem beneath the task

Migrating storage safely starts with what exists: quantities, owners, paths, file characteristics, permissions, identity matching and how people use the data.

Where it stands

The discovery and planning artifacts supported a more informed migration design. Production data movement was not represented as completed at that stage.

Explore the engineering approach
  1. Inventoried a multi-terabyte Windows file environment and reviewed its shared-folder and DFS topology.
  2. Inspected a network-attached storage platform and the intended SharePoint/OneDrive destinations.
  3. Prepared user-mapping and migration-readiness information, highlighting dependencies before any bulk transfer.
  4. Worked on discovery workbooks, decision points and pilot sequencing rather than claiming an unapproved migration was complete.
Windows File ServerDFSNASSharePointOneDrive
Related tool or script
06GOVERNANCE / APPLICATION DEVELOPMENTAssessment workflow

Making an AI governance assessment actionable

A governance engagement needed a structured way to understand staff AI use, collect tool information and turn responses into better policy decisions.

The problem beneath the task

A questionnaire is useful only if it is understandable, repeatable and produces information the organization can review and act on.

Where it stands

Survey and assessment tooling supported the discovery phase; responses and further governance decisions remained dependent on stakeholders. The work also informed a separate personal GRC architecture concept.

Explore the engineering approach
  1. Designed a lightweight web-based survey/assessment workflow to organize staff responses.
  2. Mapped the response process to AI tool inventory, risk discussion and acceptable-use policy development.
  3. Considered how a reusable workflow could reduce repeated administrative setup across similar assessments.
  4. Kept the assessment and policy decision-making separate from any claim that a web tool itself establishes compliance.
AI governanceWeb formsSurvey workflowPolicy discoveryRisk
Related tool or script
07VOICE / INFRASTRUCTURECompleted upgrade

A compact PBX capacity upgrade

A hosted business phone system required additional simultaneous-call capacity and a controlled service expansion.

The problem beneath the task

Licensing changes, platform health, recoverability and service validation needed to stay aligned without making a small upgrade unnecessarily complex.

Where it stands

The call-capacity license expansion was completed and confirmed. It is an example of a change where careful checks mattered more than building another tool.

Explore the engineering approach
  1. Reviewed the deployed VoIP platform, licensing and backup state.
  2. Applied the agreed concurrent-session capacity expansion and confirmed the license change.
  3. Validated core service health and recorded the remaining infrastructure considerations for review.
3CXVoIPLinuxLicensingBackup
08COLLABORATION / USER ENABLEMENTSupport & training preparation

Untangling file access after cloud adoption

Moving files to cloud collaboration did not automatically resolve the differences between familiar drive letters, individual OneDrive storage and team SharePoint libraries.

The problem beneath the task

Users understandably expect old workflows to remain familiar. Permissions, library locations, sync behavior and documentation are all part of the adoption problem.

Where it stands

Permission issues and user guidance informed follow-up work; broader training and migration stages were scheduled separately.

Explore the engineering approach
  1. Investigated access permissions and mapped-drive behavior across personal and team-based cloud storage.
  2. Prepared user-focused demonstrations and documentation to explain where content belongs and how to access it.
  3. Supported troubleshooting and readiness work for broader migration and adoption tasks.
SharePointOneDrivePermissionsDocumentationUser adoption
Related tool or script
WHAT THESE PROJECTS INSPIRED

The tools behind the work.

A series of practical applications, validation scripts and engineering experiments grew out of these recurring patterns.

Visit the tools & builds catalogue ↗