Integrations & Data

Microsoft's directory sends no field saying an address was verified, because it does not need one — a work address exists only on a domain the organisation proved it owns. Except for guests.

One Microsoft sign-in button serves a corporate directory account and a personal one, and the profile it returns is the same shape for both. Knowing which way that decision went tells you what the button can enforce.

A connection can hold an address, be switched on, and have proved it works — three separate facts. Collapsing them into one green tick is how a screen claims something nobody ever checked.

Social sign-in is safe when the provider says the address was verified. Microsoft's directory interface does not carry that field at all, which turns a one-line check into a question about what a corporate username proves.

Two separate parts of the product post to the same webhook and obey different rules about when to send. One is filtered by the tick boxes on the settings screen and the other is not, which reads as a bug and is correct.

Signing in, signing up and signing in from a phone must all return to one address, because that address was typed into a provider console by hand. What tells them apart is a marker.

One flag asks Airtable to make your value fit whatever the column is — and for a dropdown column, making it fit means adding a new option. The most convenient setting in the series.

The schema call identifies a table's key column by an opaque identifier. The write call wants its human name. A connector missing the translation fails on every table anybody has ever tidied.

A product with three ways to sign in has three places to forget the two-factor challenge. This one has three ways in and one place where signing in happens.

Signing in with a provider hands you an address and a claim about whether it was verified. Skip the claim and you have built an account takeover that works on anybody whose address can be guessed.

Attaching a private key to an Outlook calendar event means naming it with an identifier from the messaging API of the 1990s. Microsoft's modern interface carries it forward unchanged.

When this connector sends a purchase order from your Outlook mailbox, a copy lands in Sent Items — the actual message, in the actual folder, inside your own retention policy.