Teams chat is convenient, searchable, and often retained. Send a one-time encrypted link in Teams, not the password itself.
Create a password-protected, burn-after-read link and paste only that link into Teams. Send the additional passphrase by phone, Signal, or another independent channel. Use textdrop.sh to make the link in your browser, then share the link instead of the sensitive text.
Burn-after-read and password protection are enabled. Share the link in Teams and the passphrase separately.
Teams conversations can be retained, searched, and included in compliance or eDiscovery workflows, depending on your organization's configuration. A password pasted into chat becomes another durable copy of a live credential.
A one-time link changes what Teams stores: the chat contains a URL, not the secret. After the intended recipient reads it, burn-after-read removes the encrypted paste, leaving an unusable link in the retained conversation.
Do not send the password itself in Teams. Chat messages may be retained and searchable. Send an encrypted one-time link instead, then share any additional passphrase through another channel.
No. textdrop.sh separates metadata from encrypted content, so a link preview does not fetch the ciphertext or consume the one-time read.
Use a password manager's shared vault or your organization's access-management system. One-time links are for short, human-to-human handoffs, not ongoing credential distribution.