Skip to content

Commit 2596c16

Browse files
authored
Merge pull request #107 from cabinetoffice/cloud-recharge-policy
revision of cloud recharge policy
2 parents 987b75b + 434d664 commit 2596c16

7 files changed

Lines changed: 125 additions & 101 deletions

File tree

source/docs/cloud/aws-cloud/aws-recharge-policy.html.md.erb

Lines changed: 0 additions & 46 deletions
This file was deleted.

source/docs/cloud/azure-cloud/azure-recharge-policy.html.md.erb

Lines changed: 0 additions & 39 deletions
This file was deleted.
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: AWS hosting recharge policies (FY 2026 to 2027)
3+
last_reviewed_on: 2026-04-30
4+
review_in: 12 months
5+
---
6+
7+
# AWS hosting recharge policies (FY 2026 to 2027)
8+
9+
We recharge all Amazon Web Services (AWS) hosting costs to your service team. When you request a new AWS account, you must provide:
10+
11+
* your organisation's cost code
12+
* contact details for your finance representative
13+
* contact details for your technical lead
14+
15+
## **Recharge model**
16+
17+
The recharge includes:
18+
19+
* 100% of your AWS account cost
20+
* a 5% service fee
21+
* shared platform infrastructure costs (about 2% pro rata)
22+
* Enterprise support costs (about 7% to 10% pro rata, based on total spend across the Cabinet Office)
23+
24+
## **Overall discount**
25+
26+
Your service team receives a net discount of about 8% on AWS costs.
27+
28+
We calculate this by taking the 22% OVGA2 discount and subtracting the 5% service fee, 2% infrastructure cost, and 7% Enterprise support cost.
29+
30+
## **What the charges cover**
31+
32+
### **Cross-government discount**
33+
34+
The Cabinet Office uses the cross-government OVGA2 AWS contract to secure a 22% discount. We pass this discount directly to your account. This saving offsets the 5% service fee.
35+
36+
### **Security and compliance**
37+
38+
The service fee and shared platform costs fund central security controls. This includes threat monitoring from the Cabinet Office Security Operating Centre (SOC), automated compliance checks, and standard security guardrails.
39+
40+
These controls ensure all accounts meet government data protection standards. This means you do not have to build these security services yourself.
41+
42+
### **Contract management**
43+
44+
The service fee covers the administration of the AWS contract. This includes vendor relations, centralised billing, financial reporting, and account provisioning. This removes the administrative and procurement burden from your service team.
45+
46+
### **Shared infrastructure and support**
47+
48+
Sharing costs gives your team access to 24-hour AWS Enterprise Support and foundational infrastructure managed by the Platform Engineering team. Sharing these costs pro rata makes high-tier enterprise resources affordable and accessible to all teams, regardless of their size.
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Azure hosting recharge policies (financial year 2026 to 2027\)
3+
last_reviewed_on: 2026-04-30
4+
review_in: 12 months
5+
---
6+
7+
# Azure hosting recharge policies (FY 2026 to 2027)
8+
9+
We recharge all Azure hosting costs to your service team. When you request Azure subscriptions and tenancies, you must provide:
10+
11+
* your organisation's cost code
12+
* contact details for your finance representative
13+
* contact details for your technical lead
14+
15+
## **Recharge model**
16+
17+
The recharge includes:
18+
19+
* 100% of your Azure subscription cost
20+
* a 5% service fee
21+
* shared Azure platform infrastructure and Microsoft Unified Support costs (shared pro rata among all Microsoft and Azure tenants in the Cabinet Office)
22+
23+
## **What the charges cover**
24+
25+
### **Cross-government discount**
26+
27+
The Cabinet Office secures a 12% Azure discount through DAT21 or APA. We pass this discount directly to your Microsoft or Azure tenants. This saving offsets the 5% service fee.
28+
29+
### **Security and compliance**
30+
31+
The service fee and shared platform costs fund central security controls. This includes threat monitoring from the Cabinet Office Security Operating Centre (SOC), automated compliance checks, and standard security guardrails.
32+
33+
These controls ensure your account meets government data protection standards. This means you do not have to build these security services yourself.
34+
35+
### **Contract management**
36+
37+
The service fee covers the administration of the Microsoft and Azure contract. This includes vendor relations, centralised billing, financial reporting, and account provisioning. This removes the administrative and procurement burden from your service team.
38+
39+
### **Shared infrastructure and support**
40+
41+
Sharing costs gives your team access to 24-hour Microsoft Unified Support (which covers both Microsoft and Azure) and a robust Azure landing zone managed by the Platform Engineering team. Sharing these costs pro rata makes high-tier enterprise resources affordable and accessible to all teams, regardless of their size.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Central funding and recharge policy: Platform Services (financial year 2026 to 2027\)
3+
last_reviewed_on: 2026-01-06
4+
review_in: 12 months
5+
---
6+
7+
# Central funding and recharge policy: Platform Services (FY 2026 to 2027\)
8+
9+
Cabinet Office Digital centrally funds several platform services. You can use these resources without a direct cost to your team, provided you follow standard procurement guidelines.
10+
11+
## **Centrally funded services**
12+
13+
* standard GitHub licenses (about £30 per user)
14+
* standard domain registration through the Cabinet Office Registrar
15+
* manual SSL and TLS certificates
16+
* Docker Hub to find, share, and store container images
17+
* Hardenize to monitor domain security, including email security and web standards
18+
* Pingdom to monitor external uptime and track website performance
19+
* BrowserStack for automated and manual cross-browser and real-time mobile device testing
20+
* PagerDuty to automate on-call alerts and manage incident response
21+
22+
## **Items we recharge for**
23+
24+
We recharge your team for the following items and apply a 5% service fee to the cost:
25+
26+
* premium domains, including high-value or non-standard names
27+
* GitHub Copilot licenses and GitHub Advanced Security
28+
* specialised software, bespoke licensing, or any software and licenses not listed as centrally funded

source/docs/guidance/data-guidance.html.md.erb

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,3 @@ The "Make Better Use of Data" guidance encourages public sector organisations to
2929
### [Guidelines for AI procurement](https://assets.publishing.service.gov.uk/media/60b356228fa8f5489723d170/Guidelines_for_AI_procurement.pdf)
3030
The Guidelines for AI Procurement document provides a set of principles and best practices for public sector organisations to follow when acquiring artificial intelligence technologies. It aims to help buyers evaluate suppliers, address challenges in procurement, and ensure the ethical and effective deployment of AI systems. The guidelines also highlight the potential of AI to improve public services by reducing costs, enhancing quality, and freeing up valuable time for frontline staff.
3131

32-
## Cabinet Office standards
33-
### Minimum Enterprise Data Standards
34-
Placeholder
35-
36-
### Data Privacy Policy
37-
Placeholder
38-
39-
### Information Security Policy
40-
Placeholder

source/partials/_nav-cloud.html.erb

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,29 +3,30 @@
33
<strong>AWS</strong>
44
<ul>
55
<li><a href="/docs/cloud/aws-cloud/aws-account-tagging-schema.html">AWS account tagging schema</a></li>
6-
<li><a href="/docs/cloud/aws-cloud/aws-administration-min-requirements.html">AWS administration requirements</a></li>
7-
<li><a href="/docs/cloud/aws-cloud/aws-recharge-policy.html">AWS hosting recharge policy</a></li>
6+
<li><a href="/docs/cloud/aws-cloud/aws-administration-min-requirements.html">AWS administration requirements</a></li>
87
<li><a href="/docs/cloud/aws-cloud/aws-org-units-in-control-tower.html">AWS org units in control tower</a></li>
98
<li><a href="/docs/cloud/aws-cloud/request-new-aws-account.html">Requesting and managing a new AWS account</a></li>
109
</ul>
1110
</li>
1211

1312
<li>
14-
<strong>Azure</strong>
13+
<strong>Cloud recharge policies</strong>
1514
<ul>
16-
<li><a href="/docs/cloud/azure-cloud/azure-recharge-policy.html">Azure hosting recharge policy</a></li>
15+
<li><a href="/docs/cloud/recharge-policies/aws-recharge-policy.html">AWS recharge policy</a></li>
16+
<li><a href="/docs/cloud/recharge-policies/azure-recharge-policy.html">Azure hosting recharge policy</a></li>
17+
<li><a href="/docs/cloud/recharge-policies/central-funding-and-recharge policy.html">Central funding and recharge policy: platform services </a></li>
18+
1719
</ul>
1820
</li>
1921

2022
<li>
2123
<strong>General</strong>
2224
<ul>
2325
<li><a href="/docs/cloud/general/cloud-infra-platform.html">Cloud infrastructure and platform strategy</a></li>
24-
<li><a href="/docs/cloud/general/cloud-shared-responsibility-model.html">Cloud shared responsibilty model</a></li>
26+
<li><a href="/docs/cloud/general/cloud-shared-responsibility-model.html">Cloud shared responsibility model</a></li>
2527
<li><a href="/docs/cloud/general/domain-name-standards.html">Domain name standards</a></li>
2628
<li><a href="/docs/cloud/general/github-admin-access-policy.html">GitHub administration access policy</a></li>
2729
<li><a href="/docs/cloud/general/sandbox-policy.html">Sandbox policy</a></li>
2830
</ul>
2931
</li>
30-
</ul>
31-
32+
</ul>

0 commit comments

Comments
 (0)