The University of Michigan centrally reviews umich.edu vendor claim requests used by vendors or others to verify ownership of the umich.edu domain. Central review protects campus-wide security, privacy, and reliability, and prevents decentralized domain claims that can affect units across the university. In some cases, vendors may use DNS records for the same purpose. Any DNS record types related to vendor claims must follow this process.
Definitions
- Domain Claim: When U-M proves to a vendor that an email domain, like umich.edu, belongs to the university, so U-M can manage related accounts and settings.
- Domain Verification: A way to confirm that U-M is the rightful owner of a domain, which helps prevent others from pretending to represent the university online.
- umich.edu vendor claim: A small piece of text added to U-M's domain settings that acts like a verification code to prove ownership/control of the umich.edu domain name to a vendor.
- DNS Record Types: Vendors may ask for different types of DNS records to perform domain claims. Most commonly a TXT record, but some may use CNAME, CAA, or some other record type.
When to submit a request
Submit a request when a vendor, product, or service asks you to add a umich.edu vendor claim to umich.edu to verify the domain or claim it for account management. Common examples include verifying the domain with a SaaS product before it will allow enforcement of SSO and identity policies, consistent configuration, and consolidation of licensing and billing.
How requests are reviewed
- Domain Verifications: All umich.edu vendor claim requests for domain verification are submitted to ITS and routed to Hostmaster. Routine, single-unit, low-impact TXT verifications are approved directly by Hostmaster. Requests involving a domain claim, more than one unit, a conflict with existing central records, security, or brand are referred to the review committee.
- Domain Claims: Multi-unit domain claims are generally denied unless ITS makes the claim on behalf of the university. A single-unit domain claim may be approved on a contingent basis, with ITS retaining the right to assume control if the product's use expands.
Making a request
- Complete the DNS request in TeamDynamix (ITS-U-M-Net-DNS service). Have ready: the requesting unit and contact, the vendor or product, the exact record and value, whether it is a domain claim, and the scope of use.
- Timeline: Routine requests are usually handled within a few business days. Requests referred to the committee may take longer.
Renewal and audit
Approved records are renewed annually. ITS reviews TXT records on a regular cycle and removes records that are outdated, unused, or judged to present risk, after notice to the unit contact.
Exceptions and appeals
Units may request an exception or appeal a decision by submitting a justification through the same request. The review committee reviews and responds in a timely manner.
Questions?
Email [email protected].