Request Azure Credits#

Submit project details#

Using the cost estimate from above, the 🧑‍🔬 Project team will need to request an appropriate allocation of Azure credits. Please get in touch with the 🧑‍🔧 Trusted research system administrator team, providing the following information:

  • Project title: Name of the project

  • Research programme: Research programme that the project belongs to

  • PI name: Name of PI for this project

  • PI email: Email of PI for this project

  • Turing project code: The project code that will be used for billing. If you don’t know the project code, please ask the project PI.

  • End date: End date of project.

    • Note If your project needs to cross a financial year boundary, you may need to make two requests. Please get in touch with the Research Compute Platforms team to discuss further.

  • Research justification: A brief (100 words) research justification for this project.

  • Users who need to see costs: Names and email addresses for anyone from the project team who wants visibility of the actual spend on Azure.

    • Note: these must be email addresses associated with Turing Azure accounts.

  • Costing/Compute time breakdown: Estimated costings using the breakdowns from above

  • [Optional] Azure Subscription ID: If you already have an active Azure subscription you wish to use for the TRE.

Warning

If any of this information is missing, this will delay the start of your project.

The 🧑‍🔬 Project team should have emailed you the necessary information to make an Azure credit request. Use this to complete the Request Allocation form on Turing Complete as follows.

DSGs#

Project#

  • Project title: Suggested: Month Year Data Study Group - Data provider

  • Turing project code: Likely similar to U-DSG-022.

  • Research programme: provided by project team Usually Data Study Group

  • PI/Supervisor name: provided by project team

  • PI/Supervisor email: provided by project team

Service#

  • Which service? Azure

  • Select funding source Project/Programme budget

  • PMU Contact email address provided by project team

  • Subscription type Project

  • New or existing allocation: New (unless you are adding credit to an existing project)

  • Credits requested / £ (GBP) Enter 5/6 of the approved budget here in order to take into account VAT (20%)

  • Start date: Ensure there is enough time for building, testing and data ingress. Suggested: one month before start of DSG

  • End date: provided by project team ensure there is enough time for data egress

Information#

  • Data sensitivity: Private non-sensitive

  • Platform justification: This project is using the Turing Data Safe Haven which requires Azure.

  • Research justification: provided by project team - usually along the lines of “TRE needed for MONTH Data Study Group. Data Study Groups are collaborative, sprint-style research activities where groups of multi- disciplinary researchers need to work on datasets simultaneously.”

  • Computational requirements: This subscription will be used for a Secure Research Environment

  • Users who require access and their emails:

    • Management group: turing-safehaven-administrator@turing.ac.uk

    • Owner: Safe Haven Production Admins group

    • Reader: Safe Haven Production Readers group

    • Billing Reader: provided by project team

  • Costing/Compute time breakdown: Enter the total budgeted amount to support multiple VMs (CPU and GPU), and the associated storage and supporting infrastructure.

General Projects#

Project#

  • Project title: provided by project team

  • Turing project code: This might be R-RSE-005 or might be a project-specific code.

  • Research programme: provided by project team

  • PI/Supervisor name: provided by project team

  • PI/Supervisor email: provided by project team

Service#

  • Which service? Azure

  • New or existing allocation: New (unless you are adding credit to an existing project)

  • Start date: Use today’s date

  • End date: provided by project team

Information#

  • Data sensitivity: Private non-sensitive

  • Platform justification: This project is using the Turing Data Safe Haven which requires Azure.

  • Research justification: provided by project team

  • Computational requirements: This subscription will be used for a Secure Research Environment

  • Users who require access and their emails:

    • Management group: turing-safehaven-administrator@turing.ac.uk

    • Owner: Safe Haven Production Admins group

    • Reader: Safe Haven Production Readers group

    • Billing Reader: provided by project team

Costing#

  • Costing/Compute time breakdown: provided by project team

If you are unsure of what should go in any of these fields, discuss with the team on the #tresa channel on Turing slack.

Important

Before submitting please screenshot the page and add this to the GitHub issue you created earlier.

Subscription#

Once the subscription is created, you should get an email from the Research Compute Platforms team - note the details of the subscription name and subscription ID, which can be added the Costing section of the GitHub issue you created earlier.

Important

  • Once the subscription is created, you should email ITServices@turing.ac.uk and ask for the Safe Haven Production Admins and Safe Haven Production Readers groups to be given Billing Reader access to this subscription

  • This will allow everyone in TRESA to perform the Track budget task once the TRE is deployed