Per-org provider linking & storage discovery

Once an org has a provider OAuth app registered, each user can link their own Azure or Google account. Linking lets Eddytor enumerate that user's storage accounts/buckets and discover tables - without you hand-entering credentials.

Link an account

eddytor link provider azure     # opens the browser for consent, waits for the link
eddytor link provider google

For Azure, add blob data access (not just discovery) with:

eddytor link provider azure --azure-storage-access

The browser opens for consent; the CLI waits until the link lands.

Inspect & remove links

eddytor get providers                 # list your linked identities
eddytor unlink provider azure         # remove one

Linking vs registering storage

Two paths to give Eddytor storage access:

• Link a provider (this page) - delegated, per-user, great for discovery (browse subscriptions/accounts/buckets visually, find tables).
• Register a storage connection directly - with an access key, SAS token, service principal, or managed identity. Best for unattended / server-side access that isn't tied to a person's login.

Next

• Connect storage · Azure Blob.