I build PowerShell and Python tooling for repeatable Microsoft 365 and SharePoint analysis, access reviews and lifecycle planning at RCUM.
Executive summary
I combine read-only data collection, structured reporting and cleanup simulations. I preserve access exceptions and unresolved data, and keep actual tenant changes behind separately reviewed execution decisions.
PowerShellPythonMicrosoft GraphPnP.PowerShellSharePointMicrosoft Entra ID
Technical architecture
Problem
I need a consistent view of site activity, storage, licensing, ownership and membership before recommending operational changes.
I need to distinguish an inaccessible or incomplete record from a confirmed finding.
I need cleanup plans that preserve ownership and can be reviewed before execution.
What I built
I implemented read-only collection and reporting workflows using Microsoft Graph and PnP.PowerShell.
I combined activity, storage, licensing, ownership and membership data into structured datasets and Excel reports.
I developed access-cleanup planning and simulation workflows with fresh-state checks, audit logs and last-owner protection.
I preserved partial-access exceptions and unresolved data alongside the results.
My role
I design the data collection, normalization, reporting and review workflows.
I translate technical findings into traceable recommendations and explicit execution plans.
I document the available evidence and the limits of each read-only run or simulation.
Constraints
I work within the permissions available to each collection workflow.
I keep tenant identifiers, user information, membership details, internal reports and credentials private.
I do not treat a simulation or proposed cleanup as evidence of an executed tenant change.
Outcomes
I provide a repeatable reporting basis for access reviews and lifecycle decisions.
I make incomplete evidence, exceptions and proposed changes visible for operational review.
I provide cleanup simulations with safeguards that can be evaluated before any authorized execution.
Architecture decisions
I separate read-only collection, planning, simulation and execution.
I require fresh-state validation and protection against removing the last owner.
I retain auditability and partial-access exceptions instead of silently dropping unresolved records.
Public evidence
I describe the implemented reporting and simulation workflows here and in my RCUM experience record. The underlying tenant datasets, reports and execution records remain private.
Proof limits
I claim implemented analysis and reporting with documented read-only runs and cleanup simulations. I do not claim that proposed tenant changes have been executed, that every resource was accessible or that all findings have been remediated.