These practices applies to users and administrators of the Microsoft Infrastructure (MI) who are using contacts. These practices supplement the MI Policy.
Delegated OU Naming
All MI contacts are centrally managed, i.e. there are policies and practices about their lifecycle.
All MI contacts will live under OU=Contacts,DC=netid,DC=washington,DC=edu, unless vendor software requires that they be elsewhere.
Contact names in MI will conform to a c_<variable> namespace, and are considered part of the UW NetID namespace.
A name of the form c_<emailaddress> will be used for most contacts, where <emailaddress> is the destination email address with an underscore (_) substituted for the AT sign (@), e.g. c_barkills_cac.washington.edu. Some use cases may not be able to conform to this namespace, and naming for these use cases will be determined on a case by case basis.
Until there is a central provisioning and lifecycle mechanism, contacts:
- for Exchange email forwarding are permitted and will be manually created, modified, and deleted by the MSCA service
- for Sharepoint alerts are permitted and will be manually created, modified, and deleted by the MSCA service
Contacts for all other use cases will require further review by the MI service manager.