Duke’s planned institutional Claude service will change who controls accounts created with Duke email addresses and put some users at risk of losing access to prior conversations. The university has given affected users a transition process. As of Aug. 13, the service has not launched, account changes have not begun and many operating details remain undisclosed.
Duke’s Office of Information Technology announced Aug. 6 that the university had reached an agreement with Anthropic and planned to claim the `duke.edu` domain. A follow-up Aug. 13 described a 60-day transition scheduled to begin Aug. 17 and said the enterprise service would become available that day.
One domain, different account outcomes
Accounts using a NetID-formatted Duke address were slated to become accounts inside Duke’s managed Enterprise environment. People who had created Claude accounts with other Duke-address formats, including first-name and last-name addresses, were told to export their information and detach or change the address. Duke warned that after the transition period, non-NetID accounts tied to the claimed domain could become inaccessible and unexported content might no longer be available.
The change would affect Duke University and Duke Health users because they share the same email domain. Duke attributes the inability to separate those populations to Anthropic’s identity-management system. The decision to establish the enterprise environment and claim the domain belongs to Duke. No public notice identifies an individual who authorized the change, so responsibility should remain institutional.
The transition illustrates a problem that extends beyond Claude. An institutional email address can look like a personal identifier while remaining subject to the institution’s control. When a software provider later supports domain capture, an account created individually can move into an employer or university identity system. Users may have to export data, change addresses or accept institutional administration.
A paid service whose launch details are still pending
Duke says its Claude offering will not be free. The Aug. 13 notice says faculty and staff will use it on a pay-as-you-go basis through departmental funding and that students may use DukeCard Flex accounts. It promises additional instructions about access, funding and student options in the official launch announcement. Those are announced terms, not evidence that purchasing and access work as described.
The notices do not explain:
- whether Anthropic may use Duke Enterprise data for model training,
- how long Duke or Anthropic will retain conversations,
- which administrators may inspect account activity,
- how legal holds and investigations would affect access.
Silence on those points should remain silence. A later product description cannot be inserted into an Aug. 13 account of what users knew.
Duke also says it will provide managed Claude API access through a future Duke AI Gateway, with supported models and onboarding details to come separately. The Aug. 13 notice does not authorize protected health information, describe a HIPAA environment or define access outside Duke University and Duke Health. Users cannot infer permissions the notice does not grant.
The migration plan leaves practical gaps
Duke’s Aug. 13 instructions specify a 60-day transition beginning Aug. 17. NetID accounts are scheduled to become Duke-managed Enterprise accounts, while non-NetID Duke addresses will lose access after the transition unless users act. Duke says additional information about the NetID transition will arrive before changes occur, leaving users only four days between the detailed notice and the scheduled start.
Duke links affected users to Anthropic’s data-export instructions. It says conversations, projects, prompts, artifacts and other material will not automatically move and warns users to export anything they want to retain. The notice does not promise that an export can be imported into a new account with the same organization, links or working context.
Central management could offer a defensible security benefit by tying access to institutional identity and applying organization-level controls that consumer accounts lack. Duke has not yet published the controls, administrator permissions or offboarding process. The same mechanism gives the institution power over an account that a user may have filled with personal research, drafts or conversations before the enterprise agreement existed. The policy question is whether users understood that risk when they chose a Duke address.
The notices provide advance warning and an export opportunity, which weakens any claim that Duke is erasing user data without notice. Export can protect a copy while still interrupting the working history that made the account useful. Users who rely on a non-NetID Duke address also need a personal account if their work is unrelated to Duke.
What Duke has not disclosed
The university has not published the contract price, volume commitments, number of affected accounts, administrator-access model, retention settings or migration mechanism. Because the transition has not started, there are no public results showing how many users moved successfully, changed addresses or lost access. Without those facts, the institutional benefit and user cost cannot yet be weighed.
The defensible Aug. 13 finding is a planned operational change. Duke OIT intends to launch a managed, paid Claude environment and claim institutional control over accounts using its domain, while giving users a limited period to preserve or separate their data. The security benefits are plausible. The service and its human consequences have not yet been tested in use.