New Cloud Account Request Form | Cloud Account Database

Before You Begin

To fill out the form you will need the following information. 

• The cloud provider and intended account name.
• A short explanation of the workload and its purpose.
• Owner, technical, security, and financial contacts. Use an @wisc.edu email
• A valid DoIT Billing Customer ID (BCID), such as ICUS0001234.
• An estimated billing alert threshold. AWS and GCP use a monthly threshold; Azure uses an annual threshold.x
• The highest data classification the workload will contain.
• Research or NIH STRIDES information, when applicable.

The account request form is available from accounts.cloud-services.wisc.edu by selecting New Request. Or going directly to accounts.cloud-services.wisc.edu/requests/new

An FAQ on requesting accounts can be found here https://kb.wisc.edu/public-cloud/104090

Complete the Request

1. Name the account. Use lowercase letters, numbers, and hyphens, with no more than 25 characters. A useful pattern is school-department-purpose. Wait for the availability check to finish.
2. Describe the workload. Explain what the account will host and be used for. 
3. Select the organization and provider. Choose the school, college, or division; department or group; cloud provider; account type; AI/ML use; and whether vendor grants or credits apply.
4. Complete conditional fields. Research requests require a grant source and may include an optional Cloud Computing Project ID. Selecting NIH (STRIDES) requires the Program Officer, NIH grant number, and STRIDES follow-up fields shown by the form.

Validate Required Contacts

Enter an @wisc.edu email address. The form replaces it with the directory-authoritative email, name, and NetID. NetID and name are read-only because they come from the directory.

• Select I am the owner when appropriate.
• Use an address for an individual person. Group or shared addresses that do not resolve to one Entra user will not validate.
• At least two distinct people must be represented across the contact roles.
• Leave each contact card to validate it. Selecting Submit Request also repeats validation for every role.

Billing and Governance

Enter ICUS or CUS followed by exactly seven digits. The form removes spaces, normalizes case, and displays the BCID in uppercase.

After a valid BCID is entered, the form previews Finance FDM information. When found, review the company, cost center, FDM department, fund, function, and driver worktag. After the request is saved, CAD refreshes the account record from the Finance source.

Enter a positive whole-dollar billing alert threshold. AWS and GCP alerts are monthly; Azure alerts are annual. Alerts may lag by up to three days and do not stop or cap spending.

Finish the support selection, data classification, notes, and billing agreement. Select every applicable data classification. Restricted or Sensitive data requires an appropriate Cybersecurity risk review, and business-level support may add cost.

Submit and Track the Request

1. Review the form. Correct any visible account-name, contact, BCID, or Finance errors.
2. Select Submit Request once. The app temporarily disables the button while completing every lookup. If a check needs attention, the form returns to and focuses that field.
3. Save the confirmation. A successful submission creates a Pending account record. The confirmation page provides View Request Record, Submit Another Request, Open Jira Request.
4. Watch for follow-up. The cloud team may contact the requestor or listed contacts for clarification. Cloud Services normally responds within one business week with next steps or provisioning details.

Troubleshooting