Choose a sign-in method
The Add button in Connection Manager opens a four-step wizard: pick a method, enter environment details, enter credentials, then test and save. Step 1 offers six methods. Four of them work in 1.2.0; two are listed but do not function yet.
The six methods
| Method | How it signs in | What it needs |
|---|---|---|
| OAuth — Authorization Code (MFA) | Interactive browser sign-in with MFA support. Marked Recommended in the wizard. | Tenant ID and a client ID; the redirect URI is prefilled. |
| OAuth — Client Credentials | App-only sign-in with a client ID and client secret. | A full app registration with admin consent. |
| Certificate-based | App-only sign-in with a client ID and a certificate thumbprint from the CurrentUser\My store. | A full app registration with admin consent. |
| Username / Password | Microsoft 365 username and password with a client ID. Simple but less secure, per the wizard. | Tenant ID and a client ID. |
| Managed Identity | Azure managed identity. | Listed, but does not work in 1.2.0. |
| Connection String | A pre-built connection string. | Listed, but does not work in 1.2.0. |
For client credentials and certificates, create the app registration first: Entra app registration covers the permissions and consent, and Certificate vs client secret helps you pick the credential type. Interactive sign-in and username/password need no registration walkthrough — the wizard asks only for the IDs and sign-in details.
Managed Identity and Connection String do not work in 1.2.0
Both methods appear in the wizard, and Test Connection reports success for them, but that success is not real: in 1.2.0 these two paths return a placeholder result without contacting anything. Do not rely on them. See Known limitations in 1.2.0.
Notes for 1.2.0
- Click Test Connection before finishing. If you save without testing, the wizard warns you first.
- In 1.2.0 the wizard confirms the connection on screen but does not store it as a reusable profile in Connection Manager.
- When a test fails, the error is logged; see Sign-in errors.
What the audit actually uses
The wizard is a connectivity tester. Flow Auditor does not read Connection Manager profiles in 1.2.0 — it signs in with the Authentication section of appsettings.json next to the executable (or PowerToolBox_ environment variables): tenant ID, client ID, and a certificate thumbprint or client secret, which is an app-only sign-in. Interactive methods from the wizard do not carry over to the audit. See Entra app registration and the configuration reference.
Last updated: July 27, 2026