Windows NT and Exchange 5.5
Where my experience began: Windows NT servers and domains, and Exchange 5.5. It predates my certification record, which starts in the Windows 2000 era.
Microsoft cloud · infrastructure · identity · security
Architecture grounded in implementation.
I’m Palanikumar Annamalai, a Microsoft Cloud, Infrastructure, Identity & Security Architect based in Doha, Qatar. I connect architecture decisions to the realities of migration, coexistence, security, operations and recovery.
I have designed, implemented, migrated, secured and supported Microsoft environments acrossIndia, the UAE, Ireland and Qatar. I hold the CISSP credential, am a Microsoft Certified Trainer and previously worked as a Microsoft Cloud Solution Architect for Security in Dublin.
How I work
Connecting architecture decisions to operational reality
Some organisations are protecting established Active Directory and Windows Server estates. Others are moving identity, messaging and workloads to Microsoft cloud services. Many operate both at the same time.
I look beyond the target architecture to the dependencies, coexistence period, security controls, monitoring, support model and recovery process required to make a change sustainable.
I am particularly interested in work that crosses product boundaries: hybrid identity, messaging, infrastructure and cloud, security operations, governance, automation, assessment and validation.
International experience
Four cities. One connected Microsoft career.
India → UAE → Qatar → Ireland → Qatar
- Madurai, IndiaInfrastructure foundations and Lunar Systems
- Dubai, United Arab EmiratesEnterprise messaging and systems management
- Doha, QatarInfrastructure, identity and security
- Dublin, IrelandAzure infrastructure and Microsoft security
- Doha, QatarIdentity and messaging
Enterprise engineering
Successive generations of Microsoft technology
My early infrastructure work included Windows NT, Exchange 5.5, Windows Server, Active Directory, Small Business Server, proxy services and connectivity for remote offices. In Dubai, I moved into large-scale enterprise messaging across Exchange, Lotus Notes and Linux mail systems, including directory integration, cross-forest migrations and consolidation across successive Exchange generations.
In Qatar, my scope expanded into infrastructure security and identity. At Dell Technologies in Dublin, I worked with Windows Server, Storage Spaces Direct and certified Azure Stack HCI hardware, now part of Azure Local. At Microsoft, I supported partners with architecture, implementation, troubleshooting and optimisation across Microsoft Entra, Defender, Sentinel, Purview and the wider Microsoft security platform.
Technology progression
Each generation built on the last
The products changed names and architectures; the work did not. The stages below are in order, they overlap, and they are not dated.
- Windows NT
- Active Directory
- Exchange
- System Center
- Clustering
- Storage Spaces Direct
- Hybrid
- Azure
- Azure Local
- Microsoft 365
- Identity
- Security
- AI-era security
Windows Server and Active Directory
The move from NT domains to Active Directory, then successive Windows Server releases. Each generation brought upgrades, domain migrations, and the work of finding everything that depended on the old one.
Exchange generations and messaging
Exchange from 5.5 onwards: upgrades and mailbox migrations from version to version, and the coexistence problems of running two generations at once.
System Center and enterprise management
Managing estates at scale with System Center: deployment, configuration and monitoring, and the operational discipline that has to come with them.
Virtualisation and failover clustering
Moving workloads from physical servers to virtual machines and clustering them for availability: quorum, witnesses, and what survives a node failure.
Storage Spaces Direct and software-defined infrastructure
Clustered Windows Server with local disks pooled into resilient storage: resiliency choices, capacity planning, and reading what the cluster reports when a disk or node fails.
Hybrid infrastructure and cloud
Connecting on-premises estates to cloud services: hybrid identity, Exchange hybrid, and the decisions about what moves and what stays.
Azure
Azure infrastructure alongside what still runs on-premises, and an operating model that has to work across both.
Azure Local
Storage Spaces DirectAzure Stack HCIAzure Local
At Dell (2020–21) and then at Microsoft as a Cloud Solution Architect (2021–24), my hands-on work was Azure Stack HCI and Windows Server with Storage Spaces Direct. Microsoft renamed Azure Stack HCI to Azure Local on 19 November 2024; the clustering and storage underneath are still where much of the troubleshooting happens.
Microsoft 365
Exchange Online, Teams and the Microsoft 365 services that replaced much of what used to run on-premises, and the administration and migration work that comes with them.
Microsoft identity and access
Microsoft Entra ID and hybrid identity: authentication, Conditional Access, identity governance and Privileged Identity Management.
Microsoft security and governance
Microsoft Defender, Sentinel and Purview: security operations, and data and security governance built on Zero Trust principles.
Identity and security in the AI era
Where the work is now: passkey-first authentication, retiring legacy protocols before they are switched off, and applying identity, data and access controls to AI agents.
What it taught me
Lessons from repeated transitions
Every generation brought a new product. The engineering lessons kept repeating.
Every migration is a dependency hunt
The plan is only as good as the inventory of what depends on the old system. The dependency nobody listed is the one that fails on cutover night.
The old layer never really leaves
Azure Local still runs on clustering and storage. Entra ID still meets Active Directory in hybrid identity. Knowing the layer underneath is most of the troubleshooting.
Coexistence is where the risk sits
Running two generations side by side, sometimes for months, is harder than either the old estate or the new one.
Names change faster than architectures
Knowing what a product used to be called is often how you find the right documentation, the right log and the right fix.
Identity is the control plane
From NT domains to Entra ID, whoever controls identity controls everything else. Security work starts there.
Automate the second time
The first run teaches the process. The script makes it repeatable, reviewable and teachable.
The work that recurs
- Implementation
- Migration
- Upgrades
- Transitions
- Architecture
- Troubleshooting
- Operational ownership
- Identity
- Messaging
- Infrastructure
- Security
- Automation
Current focus
Five areas I work in today
My perspective connects Azure Local and Entra ID with the Windows Server, Active Directory, clustering and messaging foundations underneath them. That is the experience I bring to my writing and training.
Infrastructure and hybrid cloud
Windows Server estates, clusters and software-defined storage, and how they extend into Azure and Azure Local.
- Windows Server
- Active Directory
- Failover Clustering
- Storage Spaces Direct
- Azure
- Azure Local
Identity and access
From Active Directory to Microsoft Entra ID: hybrid identity, authentication, Conditional Access and privileged access.
- Microsoft Entra ID
- Hybrid identity
- Conditional Access
- Identity governance
- Privileged Identity Management
Messaging and collaboration
Exchange since 5.5: on-premises generations, Exchange hybrid, Exchange Online and the Microsoft 365 around it.
- Exchange Server
- Exchange hybrid
- Exchange Online
- Microsoft 365
- Teams
Security and governance
Security operations, identity security and data governance, built on Zero Trust principles rather than bolted on.
- Microsoft Defender
- Microsoft Sentinel
- Microsoft Purview
- Zero Trust
Automation and technical enablement
PowerShell and Microsoft Graph for the repeatable work, and labs, scripts and training so others can do it too.
- PowerShell
- Microsoft Graph
- Labs and scripts
- Training
Selected credentials
Credentials aligned with architecture, security and operations
These certifications validate the security, architecture, cloud and identity disciplines most relevant to my work. The broader certification record is available on Credly.
Technical training and presentations
Microsoft Certified Trainer
Recorded AZ-900, AZ-104 and SC-200 training series, and technical presentations. Training
Professional certification
- CISSPCertified Information Systems Security Professional
Expert certifications
- SecurityMicrosoft Certified: Cybersecurity Architect Expert
- CloudMicrosoft Certified: Azure Solutions Architect Expert
- Microsoft 365Microsoft 365 Certified: Administrator Expert
Associate certifications
- IdentityMicrosoft Certified: Identity and Access Administrator Associate
- SecurityMicrosoft Certified: Azure Security Engineer Associate
- Security operationsMicrosoft Certified: Security Operations Analyst Associate
- CloudMicrosoft Certified: Azure Administrator Associate
Microsoft Applied Skills
- Configure SIEM security operations using Microsoft Sentinel
- Secure Azure services and workloads with Microsoft Defender for Cloud regulatory compliance controls
As of September 2026
- active Microsoft certifications
- 18
- passed Microsoft exams
- 32
- Microsoft Applied Skills
- 2
Certification history
A record across generations
Selected technology areas from my Microsoft exam history, from the Windows 2000 era to today. The work itself started earlier, with Windows NT and Exchange 5.5.
- Windows 2000
- Windows 2000 Directory Services
- Exchange Server 5.5
- Proxy Server
- Active Directory
- Windows Server
- Exchange Server 2010
- System Center
- Lync
- Windows Server infrastructure architecture
- Azure
- Microsoft 365
- Identity
- Security operations
- Cybersecurity architecture
Community
Training
I am a Microsoft Certified Trainer, and I treat teaching as part of the engineering work: if I cannot explain it clearly, I do not understand it well enough.
Standards
How I publish
- Versions and validation. Technical guides state the applicable product versions, validation status and limitations so readers can judge whether the guidance fits their environment.
- Limitations stated. Labs and resources say what they do not cover, and where they will give you a wrong answer.
- Case studies anonymised. Employer and customer details are removed, and nothing is published without approval.
- Names as they were. Microsoft renames products often. I use the name that applied at the time of the work.
- 4countries worked
- CISSPsecurity credential
- MCTMicrosoft Certified Trainer
- Ex-MicrosoftCloud Solution Architect
Beyond the architecture diagrams
Curiosity, community and conversation
Technology has always been practical and social for me: learning by building, exchanging ideas and staying close to the systems and people affected by an engineering decision.
Where the interest began
A practical interest in how systems work
My interest in technology began with electronics, early personal computers and learning through experimentation. Building and repairing computers, supporting schools and developing a small FoxBASE accounting application gave me an early appreciation for technology that solves a real problem for a real user.
That background remains part of how I approach engineering, but my professional focus today is enterprise Microsoft architecture, identity, security, operational resilience and technical enablement.
Contact
Connect
I’m open to senior architecture, technical leadership, speaking and Microsoft training opportunities. For professional enquiries or questions about material published here, email is the best way to reach me. I also share shorter technical notes on LinkedIn.