Available for opportunities · Brisbane, QLD
AP

Arun Pandey

System Administrator

Cloud infrastructure and security engineer with hands-on experience designing and administering Azure, Microsoft Entra ID and Microsoft 365 end to end: hybrid-to-cloud identity migrations, Conditional Access and MFA rollouts, automated user lifecycle management, and multi-region enterprise storage architecture, grounded in ISMS (ISO 27001) and ITIL-aligned operations.

AZ-104 Microsoft Azure Administrator SC-900 Security, Compliance & Identity Fundamentals CEH Certified Ethical Hacker

About

01

What I actually enjoy is the moment a messy environment starts making sense: a fleet of devices still tangled in on-prem AD dependency, a file share that's fast in one region and painful in another, an onboarding process held together by tickets and memory. Untangling that, deciding what the identity model should be rather than just patching around it, and watching the fix hold up months later. That's the part of this job I'd do for free.

Outside of work hours, I'm usually solving a different kind of problem in a very different kind of environment. Rock climbing has the same appeal as a good architecture decision: read the terrain, commit to a line, adjust when it's wrong. Bushcraft scratches a similar itch: no dashboard, no rollback, just first principles and whatever's actually in front of you. I write when I need to think something through properly, and lately I've been deep in vibe coding, building things fast and scrappily with an AI pair, which honestly isn't that different from architecting cloud infrastructure: you're still the one who has to know why it works.

Off the clock
Rock ClimbingWriting BushcraftVibe Coding

Featured projects

02
Identity migration

Hybrid to Entra ID Identity Migration

Migrated the managed device fleet from Hybrid Azure AD Join to Entra ID Join, removing on-premises Active Directory dependency for authentication on migrated machines while preserving user state during transition.

Architecture
Devices previously Hybrid Azure AD Joined (synced via on-prem AD DS and Entra Connect) are migrated in place to Entra ID Joined only, using a ProfWiz script deployed at scale through NinjaOne to carry the user's profile, application data, and settings across the join-type change.
Tech stack
Microsoft Entra IDHybrid Azure AD Join Entra ConnectNinjaOneProfWiz
Outcome: Reduced manual per-device rebuild effort and eliminated on-premises domain dependency for authentication on every migrated machine, with no disruption to end-user profile or app state.
FIG. 01
LEGACY: HYBRID JOIN, AD DEPENDENCY Hybrid Azure AD Joined Device On-prem AD DS + Entra Connect sync ProfWiz script via NinjaOne PRESERVES: user profile / app data / settings IMPLEMENTED: ENTRA ID JOIN, CLOUD-ONLY AUTH Entra ID Joined Device Only No on-prem AD dependency
WORKFLOW Start Identify Hybrid-Joined Devices Deploy ProfWiz via NinjaOne Migrate to Entra ID Join Validate & Preserve User State End

Legacy hybrid-join / on-prem AD dependency vs. implemented Entra ID-only, cloud-only auth.

Enterprise storage architecture

Enterprise File Storage Migration: Azure Files, Azure NetApp Files & Regional Cache VMs

Designed a distributed storage architecture giving both AU and US-based engineering staff local-speed file access against a single centralised SolidWorks data source, spanning two genuinely different identity/authentication models depending on the underlying storage service.

Architecture
Azure Files authenticates via Microsoft Entra Kerberos: cloud-only devices need no Domain Controller at all; hybrid devices need one only for ACL/permission resolution. Azure NetApp Files, by contrast, has no Entra Kerberos support and is bound to on-prem AD DS, requiring a reachable Domain Controller for every SMB session. On top of this, two regional cache VMs (AU/Sydney, US/Central US) sync against the central Azure Files share via Azure File Sync, with a logon-time latency probe auto-routing each user to whichever cache responds faster. A separate Intune Win32 dependency chain gives client devices a local working copy of SolidWorks reference folders, synced back on a schedule via Task Scheduler and Robocopy.
Tech stack
Azure FilesAzure NetApp Files Azure File SyncEntra Kerberos AD DSCloud Kerberos Trust Cloudflare WARPIntune Win32 Task Scheduler / Robocopy
Key decision: Domain Controller dependency differs materially by storage service. Azure Files (hybrid) needs a DC only for permissions, while Azure NetApp Files needs one for every session. That distinction drove which service each workload was placed on, rather than treating "file storage" as one interchangeable choice.
FIG. 02A
AZURE FILES - ENTRA KERBEROS Cloud-only device Hybrid-joined device Microsoft Entra Kerberos authentication DC - permissions only, not auth Azure Files share ~180ms/op SAME PROJECT / TWO IDENTITY MODELS AZURE NETAPP FILES - AD DS-BOUND Domain-joined / hybrid device SMB - Kerberos via AD DS Domain Controller (corp.tritium...) Delegated subnet: VNet connectivity to AD DS required Azure NetApp Files vol-solidworks-prod-aue Ultra tier, 1000GiB No Entra Kerberos support - AD DS or Entra Domain Svcs only Azure Files: DC needed only for hybrid permissions. ANF: DC is a hard dependency every session.
WORKFLOW Start Determine Storage Workload Entra Kerberos Capable? Azure Files (Entra Kerberos) End Azure NetApp Files (AD DS Kerberos) End Yes No

Two identity models under one storage project, evaluated per workload.

FIG. 02B
Azure Files - SolidWorks share (~179GB, single source of truth) Azure Storage Sync Service (cloud + server endpoints) AU CACHE VM (SYDNEY) Latency probe: logon/unlock Auto-routes to faster cache Domain-joined Windows Server On-site users LAN Requires reachable DC (Cloud Kerberos Trust bridge) US CACHE VM (CENTRAL US) Latency probe: logon/unlock Auto-routes to faster cache Domain-joined Windows Server On-site users LAN Requires reachable DC (Cloud Kerberos Trust bridge) Remote user Cloudflare WARP Cloudflare WARP Status: LIVE - 20 SolidWorks users across AU and US, direct Azure Files + local caching.
WORKFLOW Start Run Logon Latency Probe AU or US Faster? Route to AU Cache VM End Route to US Cache VM End AU US

Regional cache VMs, Azure File Sync, and logon-time latency-based auto-routing.

FIG. 02C
STAGE 1: ENTITLEMENT & KERBEROS STAGE 2: INTUNE WIN32 DEPLOY STAGE 3: APPLICATION ISOLATION User DeviceEntra ID Joined only Kerberos TGT from Entra ID for DC-free UNC access User Entitlement(ACLs) Azure Files SolidWorks Share Intune Management Plane Win32: SolidWorks Cache Manager 1. DC-Free Kerberos Mapping (Z:) 2. Initial Pull Z: to C: (~7GB) 3. Scheduled Robocopy Sync User device Network Z: Local C: App reads local metadata (~180ms) Network Z: (sync target only) STATUS: validated for reference folders only, not the active-edit project share.
WORKFLOW Start Map Z: Drive (Entra Kerberos) Pull Reference Data Z: to C: Apply SolidWorks Config Task Scheduler Syncs Back to Z: End

Client-side local caching via a sequential Intune Win32 dependency chain.

Automation

Automated User Lifecycle Management

Built an end-to-end onboarding and offboarding pipeline driven entirely by a single HR CSV source of truth, removing manual ticket-driven account provisioning.

Architecture
A hybrid-joined VM reads the HR CSV to create or disable the on-prem AD account, triggers Entra Connect delta sync to propagate the change to the cloud, then applies OU placement, group membership and standard access, orchestrated end to end through Azure Runbooks and Scheduled Tasks.
Tech stack
Azure AutomationAzure Runbooks Scheduled TasksAD DS Entra Connect Delta Sync
Outcome: Removed manual, ticket-driven onboarding/offboarding steps and reduced the risk of accounts being left with stale access after a user departs.
FIG. 03
HR CSV (source of truth)HR storage account Logic App / Runbookevaluate boolean TRUE FALSE ONBOARD Hybrid-joined VMcreates on-prem AD account OU + group membership applied OFFBOARD Hybrid-joined VMdisables/removes account Cloud access + group revoked Both branches driven by Azure Runbooks and Scheduled Tasks Runbook: rb-onboarding-main.ps1 v8.4 - production
WORKFLOW Start Read HR CSV Record Onboard? Create AD Account Delta Sync + OU/Group End Disable / Remove Account Delta Sync Revokes Access End Yes No

HR CSV source of truth, boolean-driven branching, dual delta-sync propagation.

Endpoint management

Intune Department-Based Application Deployment

Replaced a flat, blanket-policy deployment model with department-scoped application and profile delivery, so devices only carry the software relevant to their team.

Architecture
Users are segmented into department-based dynamic and assigned security groups in Intune (Finance, Sales, Engineering), each mapped to its own application packages and configuration profiles rather than a single fleet-wide policy set.
Tech stack
Microsoft Entra ID GroupsMicrosoft Intune Win32 App PackagingConfiguration Profiles
Outcome: Reduced unnecessary software footprint on devices that didn't need it, with each department receiving only its relevant applications and profiles.
FIG. 04
STAGE 1: IDENTITY GROUPS STAGE 2: INTUNE POLICY STAGE 3: APP + CONFIG + DEVICE Finance Security Group(Aad-Finance-AppAssignment) Sales Security Group(Aad-Sales-AppAssignment) Engineering Security Group(Aad-Engineering-AppAssignment) User Entitlement(ACLs) Microsoft Intune Dynamics 365 Finance Secure Finance Config -> Finance-Managed Salesforce CRM Client Sales App Access Policy -> Salesforce CRM Device SolidWorks 2024 Cache Mgr Engineering App Config -> Engineering-Managed STATUS: group and policy validation complete. Each department receives only its relevant apps and profiles.
WORKFLOW Start Assign User to Dept Group Intune Applies Dept Policy Deploy App Package + Config End

Entra ID group segmentation through to department-scoped application delivery.

Additional projects

Identity & access: additional delivery

Conditional Access, MFA & SSPR Rollout

Designed and rolled out Conditional Access policies enforcing MFA based on user risk, location and device compliance signals, alongside Self-Service Password Reset with password writeback to on-premises Active Directory, implemented to Microsoft security best practices and contributing to a measurable improvement in the organisation's Microsoft Secure Score.

Enterprise Application SSO Integration

Registered and configured Enterprise Applications in Azure for Single Sign-On, published through MyApps, so users authenticate once with their Entra ID credentials instead of managing separate application logins, improving both user experience and credential security.

Experience

03

IT System and Cloud Administrator

Tritium Power Solutions, January 2024 – Present

  • Administer the hybrid Azure and Microsoft Entra ID environment: Conditional Access, MFA enforcement, RBAC at directory and resource level, and Entra Connect sync health, following Microsoft-recommended security baselines.
  • Configure and maintain Enterprise Applications in Azure for Single Sign-On, published through MyApps.
  • Manage Microsoft Purview and Defender for Office 365 for email security: audit reporting, quarantine review, and anti-phishing/anti-malware policy tuning.
  • Administer Intune MDM/MAM for the device fleet: compliance policies, configuration profiles, application packaging, and PowerShell-based proactive remediations.
  • Administer Microsoft 365 across Exchange Online, SharePoint, OneDrive and Teams Admin Centre, alongside Purview eDiscovery and sensitivity labelling.
  • Own the enterprise storage architecture and the automated user lifecycle management pipeline detailed under Projects.
  • Monitor endpoint security through CrowdStrike: device inventory, USB whitelisting, and alert investigation.
  • Manage Azure cost optimisation by reviewing usage telemetry and rightsizing or scheduling resources.
  • Maintain alignment with ISMS policy (ISO 27001) and ITIL-aligned change and incident management.

IT System Administrator

Tritium Power Solutions, January 2023 – 2024

  • Delivered day-to-day IT support across hardware, software, network connectivity and access issues.
  • Administered Miradore MDM and early-stage Microsoft Intune enrolment, applying baseline device policies.
  • Managed user onboarding through Active Directory Domain Services: account creation, group/OU membership, and new-starter hardware setup.
  • Provided remote and in-person application support via TeamViewer, Quick Assist and Microsoft Teams.
  • Administered Microsoft 365 user, group and license management, and supported early Entra ID administration as the environment began its shift to cloud identity.
  • Managed physical access control via the Access Alarms portal: FOB provisioning, alarm handling and access revocation.

IT Support

Guj-Infotech QLD, July 2022 – December 2022

  • Delivered first-line IT support: hardware/software troubleshooting, laptop and monitor deployment, and new user onboarding for a mid-sized client base.
  • Processed user access and security group membership requests per standard onboarding and change procedures.
  • Supported end users remotely and on-site, resolving hardware, software, network and access issues to minimise downtime.

Skills & credentials

04
Cloud & Identity
AzureEntra IDHybrid Identity (Entra Connect) Enterprise Applications & SSOConditional Access MFASSPRRBACIAM Directory-Level Roles
Security & Compliance
Microsoft Secure ScoreMicrosoft Purview Defender for Office 365CrowdStrike Audit ReportingQuarantine Management Network Security GroupsISMS (ISO 27001)ITIL
M365 / O365 Administration
Admin CentreExchange OnlineSharePoint OneDriveTeams Admin CentreeDiscovery Sensitivity Labelling
Endpoint & Device Management
Intune MDM/MAMCompliance Policies Application DeploymentScripts & Remediation NinjaOneBitLocker
Infrastructure & Storage
Azure FilesAzure NetApp Files Azure File Sync (Cloud & Server Endpoints)Storage Migration
Automation & Operations
Azure RunbooksScheduled Tasks PowerShellCost Management
Certifications
  • AZ-104: Microsoft Azure AdministratorMicrosoft
  • SC-900: Security, Compliance & Identity FundamentalsMicrosoft
  • Certified Ethical Hacker (CEH)EC-Council
Education
  • Master of Information Technology; Master of Business Administration, James Cook University2020–2022 · Distinction
  • Bachelor of Computer Engineering, University of Mumbai2015–2019 · Distinction

Contact

05

Open to conversations about cloud infrastructure, identity architecture, and security engineering roles, and I'm happy to walk through any of the projects above in more depth.