Cloud Workplace Engineer

About the Role

You own the company's identity provider: who signs in, from where, with which factors, into which applications — and how that access is granted, reviewed, and revoked.

Microsoft Entra ID is the primary identity plane and the center of gravity for the role. Google Workspace, Cloud Identity, and Google Cloud IAM form a second substantial domain, and you own the federation and provisioning path between them. Microsoft 365 is in scope for tenant, licensing, and access administration.

You are the escalation point for identity incidents from operations, security, service desk, and application teams — expected to resolve them, not route them onward.

What You'll Own

Microsoft Entra ID and Microsoft 365

• Users, dynamic and assigned groups, administrative units, directory roles, service principals, workload identities.
• Conditional Access design and rollout: named locations, client app and platform conditions, session controls, sign-in frequency, break-glass exclusions, report-only staging.
• Authentication methods policy and phishing-resistant factors.
• Application onboarding over SAML 2.0 (NameID, claims mapping, signing certificate rollover, encrypted assertions) and OIDC / OAuth 2.0 (authorization code with PKCE, client credentials, device code).
• App registrations: redirect URIs, permissions, admin consent workflow, secret and certificate lifecycle. – SCIM 2.0 provisioning: attribute mappings, scoping filters, expression transformations, quarantined jobs, drift reconciliation.
• Tenant consent settings, OAuth grant review, remediation of over-permissioned and stale applications; defensible controls for SaaS without SSO or SCIM support.
• Joiner-mover-leaver as an automated pipeline: provisioning, group-based licensing, revocation with session and refresh token invalidation.
• Least privilege for admin access: scoped role assignments, RBAC, PIM, access reviews, entitlement management access packages.
• Service account and workload identity governance: ownership, credential rotation, permission scoping, decommissioning.
• Microsoft 365 tenant settings, licensing, admin roles; access and permission issues in Exchange Online, SharePoint Online, Power Platform.
• Diagnostics from sign-in, audit, and provisioning logs, with diagnostic settings routed to Log Analytics and KQL queries.
• Cross-tenant access settings and B2B external collaboration.

Google Workspace, Cloud Identity, and Google Cloud

• Google Workspace and Cloud Identity: users, groups, organizational units, admin roles and privileges, licensing, 2-Step Verification enforcement, session controls.
• Third-party SSO profiles with Microsoft Entra ID as SAML IdP, automated provisioning into Cloud Identity, OU- and group-scoped SSO exclusions.
• Context-Aware Access policies, third-party OAuth app access control, domain-wide delegation, Drive sharing and external access controls. 2
• Google Cloud IAM: project and folder membership, predefined and custom roles, allow policies, service accounts and key hygiene, workload identity federation, API enablement, OAuth clients.

Automation 

• PowerShell tooling on the Microsoft Graph PowerShell SDK and Graph REST API: lifecycle, licensing, access reporting, recertification.
• Google-side automation through the Admin SDK Directory API, Cloud Identity API, and gcloud.
• Scheduled and event-driven workflows in Azure Automation Runbooks, Azure Logic Apps, or Power Automate.
• Unattended execution on managed identities and narrowly scoped app registrations, with credential rotation, structured logging, error handling, and retries.
• Automation treated as production code: version control, peer review, documented rollback.

What You'll Bring

We care about what you can do, not which products appear on your CV. Concretely, you can:

• Decode a SAML assertion or JWT and pinpoint the failure — audience mismatch, NameID format, expired signing certificate, missing claim — without escalating to the vendor.
• Diagnose a failing SCIM job and tell scoping from attribute mapping, transformation expressions, or target schema.
• Replace a manual lifecycle process with automation that logs, retries, and can be handed to someone else to run.

Experience We Expect

• 3+ years administering Microsoft Entra ID in production as a primary responsibility.
• Enterprise applications, app registrations, consent and permission models, automated provisioning.
• Microsoft 365 administration: tenant settings, licensing, admin roles, and access troubleshooting across Exchange Online, SharePoint Online, and Power Platform.
• Google Workspace and Cloud Identity administration: organizational units, groups, admin roles, SSO profiles, access settings.
• Google Cloud IAM: projects, roles and policies, service accounts, API access, OAuth credentials.
• Strong PowerShell with the Microsoft Graph PowerShell SDK and direct REST API work.
• Azure Automation Runbooks, Azure Logic Apps, Power Automate, or comparable platforms.
• Least privilege, secure administration, change management, and the discipline to leave configurations documented.
• Written and spoken English at B2 or higher

Nice to Have

• SC-300, MS-102, or SC-401 — or equivalent demonstrable expertise.
• Microsoft Entra ID Governance: entitlement management, lifecycle workflows, Privileged Identity Management.
• Microsoft Purview (DLP, retention, eDiscovery), Microsoft Defender for Cloud Apps, or Microsoft Sentinel.
• Google Cloud workload identity federation, custom roles, organization policy constraints.
• Git, CI/CD practices, Pester, Bicep, or Terraform.
• Access evidence for SOC 2, ISO 27001, or comparable audit cycles.