Date: Thu, 28 Mar 2024 18:58:06 +0000 (UTC)
Message-ID: <1023656041.6815.1711652286873@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_6814_835368861.1711652286872"
------=_Part_6814_835368861.1711652286872
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Account onboarding practices (MOUs, AUAs, etc.)
Account onboarding practices (MOUs, AUAs, etc.)
Every institution has its own way it onboards and manages its ac=
counts. Some pay the vendor with a single PO and rebill internally. Others =
have direct billing to their account holders. Some schools create special T=
s & Cs for their users while other cover them with existing AUAs. This =
page is a place where schools can share their practices so we can learn fro=
m each other.
Ind=
iana University
AWS
- IU sets up accounts for its users to be direct billed by the reseller. =
Internal rebilling comes at a cost and we want to keep the price for the us=
ers as low as possible.
- If a user or department wants to get an account with one of the cloud v=
endors the person responsible for the funding source must sign IU's Public Cloud Acceptable Usage Agreement. When they sign the agreeme=
nt and indicate which platform(s) they are interested in, they are emailed =
instructions for producing an IU purchase order to fund their account.
GCP
GCP Configuration Proposal
Penn State<=
/h3>
- Billing is done via a single PO and processes chargeback internally.
- Penn State's account request form requires agreeme=
nt to a built-in attestation and billing information.
------=_Part_6814_835368861.1711652286872--