Cloud Readiness leads
- #13 TST Smoke Test (Xperters E2E Lane) You run all services on physical servers in your office for ~20 staff and already use Microsoft 365. This is primarily an On-premises to Azure migration need, with a strong Microsoft Entra ID / identity and access management component and a place for General Azure cloud engineering. I also recommend Infrastructure-as-code (Terraform/Terragrunt) as a best practice for the target environment. Because you haven't provided an inventory of servers, applications, who manages IT, or whether any data is sensitive, a short technical discovery is required before detailed planning. 16-AUG-2026
- #12 TST Smoke Test (Xperters E2E Lane) You are a small business (≈20 staff) still running everything on physical servers in your office and using Microsoft 365. The most relevant engagement areas are: On‑premises to Azure migration (moving those servers/applications), Microsoft Entra ID / identity (because you already use Microsoft 365), and General Azure cloud engineering (architecture, connectivity, backup, security). A short discovery is needed before deciding on Infrastructure-as-Code or CI/CD work. 16-AUG-2026
- #11 TST Smoke Test (Xperters E2E Lane) [e2e-test] 632be03bfdb9476fb0e129c0627dac9e 16-AUG-2026
- #10 TST Smoke Test (Xperters E2E Lane) You run all services on physical office servers for ~20 staff and already use Microsoft 365. This is primarily an On‑premises to Azure migration need, with a clear follow-up requirement for Microsoft Entra ID / identity and access management and general Azure cloud engineering to host, secure and operate workloads. At this stage there isn’t enough detail about what the servers actually do or whether sensitive data is stored, so a short technical discovery is the right first step. 16-AUG-2026
- #9 TST Smoke Test (Xperters E2E Lane) You are a small UK company (≈20 staff) running all services on physical servers in your office and already using Microsoft 365. The primary needs here are an on‑premises → Azure migration combined with Microsoft Entra ID / identity work (to integrate your existing Microsoft 365 tenancy and any on‑prem AD). General Azure cloud engineering is also relevant to set up networking, governance, backup and ongoing operations. Infrastructure-as-code and CI/CD are recommended later for repeatable, low‑touch operations but are secondary until we complete a discovery and an initial migration proof-of-concept. 16-AUG-2026
- #8 TST Smoke Test (Xperters E2E Lane) [e2e-test] 4ab6520703404e52957e843bd8afb7ae 16-AUG-2026
- #7 TST Smoke Test (Xperters E2E Lane) You are a small organisation (~20 staff) running all services on physical office servers and using Microsoft 365. The engagement types that fit are: On-premises → Azure migration (to replace those physical servers), Microsoft Entra ID / identity and access management (to ensure M365 and any cloud VMs/users are integrated securely), and General Azure cloud engineering (networking, backups, sizing). Infrastructure-as-code and CI/CD are optional follow-ups once you have workloads in Azure, but are not the immediate priority based on your description. 16-AUG-2026
- #6 TST Smoke Test (Xperters E2E Lane) [e2e-test] 392b2bc8f1b3421f9cfd040ab2071447 16-AUG-2026
- #5 TST Smoke Test (Xperters E2E Lane) You are a small office (≈20 staff) running everything on on‑premises physical servers and already using Microsoft 365. The primary needs that fit from our service menu are: On‑premises to Azure migration (to remove single‑site risk and hardware maintenance), Microsoft Entra ID / identity and access management (because you already use M365 and will need tenant/integration and secure access), and General Azure cloud engineering/orchestration (target architecture, connectivity, backup/DR). Infrastructure‑as‑code is a recommended follow‑up for repeatable deployments; CI/CD is not immediately required from what you described. 16-AUG-2026
- #4 TST Smoke Test (Xperters E2E Lane) You are a 20-person organisation running all services on physical servers in your office and already using Microsoft 365. The most relevant Xperters services are: On‑premises to Azure migration (to move those physical servers and data), Microsoft Entra ID / identity and access management (because Microsoft 365 implies an Azure AD/Entra relationship that will affect user accounts and authentication), and General Azure cloud engineering (connectivity, backups, sizing and operations). You want to move to the cloud but don’t know where to start — the right next step is a short technical discovery to define inventory, identity state and a small pilot migration approach. 16-AUG-2026
- #3 TST Smoke Test (Xperters E2E Lane) You are running about 20 staff from physical servers in your office and already use Microsoft 365, and you want to move to the cloud but don’t know where to start. The most relevant Xperters services are: On‑premises to Azure migration (to move your existing servers), Microsoft Entra ID / identity and access management (to align your Microsoft 365 identity with Azure), and General Azure cloud engineering and orchestration (to design a secure, supported landing zone). Infrastructure‑as‑Code and CI/CD may be useful later but are not the immediate priority based on what you described. 16-AUG-2026
- #2 TST Smoke Test (Xperters E2E Lane) [e2e-test] ecde0df294ac4bb08355c9138cc31cfd 16-AUG-2026
- #1 TST Smoke Test (Xperters E2E Lane) [e2e-test] a6163f51dddd48dea70d9d5491dc1a5d 16-AUG-2026