How access is granted
Access arrangements are flexible: a guest account, temporary credentials or delegated access, depending on your security requirements.
- Guest account
- Temporary credentials
- Delegated access
For whoever looks after your systems
Working with your IT team
What your IT or security lead will want to know before work starts: how I get access, how your data is protected, how changes reach your environments, and what you are left with at the end. All work is delivered remotely, inside your access model and governance.
Access
Access on your terms
I work within your access model and governance, and I do not make changes without your agreement.
Identity and remote working
I can authenticate with Microsoft Entra ID (Azure AD), GitHub and Google Workspace identities, work within virtual desktop or restricted environments with no local installation required, and join your Microsoft Teams tenant as a federated guest for the length of the work.
- Microsoft Entra ID
- GitHub
- Google Workspace
- Azure Virtual Desktop
- Windows 365
- VDI
Security and data protection
Your data, handled with care
Security and GDPR requirements are considered at the design stage. UK data protection obligations are addressed before code is written, not after.
- PageTech Solutions Limited is registered with the Information Commissioner’s Office (registration no. ZC179729).
- The company is insured with Hiscox, including cyber and data cover. The full list of cover is in the FAQ.
- See the privacy notice for how this site handles personal data.
Environments
Changes through your environments
I can work directly inside your Azure subscription or GitHub organisation: diagnosing failures, reviewing CI/CD pipelines and advising on configuration.
Platforms
Azure App Service, Functions, SQL Database, Static Web Apps and Azure DevOps, and GitHub organisations. CI/CD pipelines, build automation and deployment scripting can be scoped as part of a wider piece of work.
- Azure App Service
- Azure Functions
- Azure SQL
- Azure Static Web Apps
- Azure DevOps
- GitHub
You stay in control
For provisioning, I advise on what to create and how to configure it; you approve and execute changes in your subscription. My own systems ship through automated, environment-gated promotion from dev to testing to production, with no direct-to-production deploys: how this site is built shows it end to end.
Handover
What you are left with
- Low-level design, documentation and knowledge transfer: everything you need to own and operate the solution. The 30-day warranty period starts from sign-off.
- Once the work has been paid for in full, the code written specifically for you is yours to keep, modify or share, with no ongoing licence fee. Written findings are yours whether or not you commission the work that follows them.
- See knowledge transfer for how the handover is put together.
Next steps