Your Microsoft connection in Tackle currently uses a client secret, which expires. Updating the connection replaces it with a password-free connection that stays active without manual renewal.
The update takes about 5 minutes. Your connection stays active while you complete it.
Only see “Action Required” on your Microsoft tile? Follow the steps below. If your Microsoft tile shows Connected with no Action Required tag, your connection is already up to date and you don’t need to do anything.
New to Microsoft in Tackle? Follow Connect to Microsoft instead.
Before you begin
You’ll need:
Tackle: Administrator role, or a custom role with Administrator privileges.
Microsoft: Global Admin access to the Azure tenant that contains your existing Tackle app registration.
Azure Cloud Shell: Access at shell.azure.com, set to Bash (not PowerShell).
Azure subscription: An active subscription (Pay-As-You-Go or Free Trial). Cloud Shell needs one to create a small storage account. The cost is typically a few cents per month.
If you need help gathering these permissions, schedule time with the people who have them.
How this update works
Your Azure Tenant ID and Application ID don’t change.
You don’t need to re-authorize Partner Center, redo marketplace setup, or re-grant admin consent.
The update adds a federated identity credential to your existing Azure app and registers it with Tackle. Tackle stops using the stored client secret once it’s registered.
You don’t need to delete your Azure client secret.
Step 1: Open the Microsoft integration in Tackle
Sign in to Tackle as an Administrator.
Select Integrations.
Find the Microsoft tile, which shows Action Required (usually next to Connected).
Select Configure, or select Update now in the banner.
Step 2: Copy the update command
Expand Step 1: Connect to Microsoft if it isn’t open.
Under 1a. Copy update command, select the copy icon.
Step 3: Run the command in Azure Cloud Shell
Sign in to the Azure Portal as a Global Admin.
In Tackle, select Launch Cloud Shell, or open shell.azure.com directly.
At the top left of Cloud Shell, confirm Bash is selected.
Paste the command and press Enter.
Return to Tackle. It will wait for the connection to be established, which can take up to about 5 minutes.
Step 4: Confirm the update
When the update succeeds, you’ll see:
What you’ll see | Expected result |
Microsoft tile | Action Required is gone |
Connection details → Auth Method | Workload Identity Federation |
Connection details → Tenant ID and Application ID | Unchanged |
Troubleshooting
Re-running the update command is always safe. It won’t create duplicate resources.
Insufficient privileges
You must be signed in as a Global Admin on the correct tenant. Ask your Azure administrator for the role, or have them run the command for you. Then copy the command again and re-run it in Bash.
Wrong Azure tenant
In Cloud Shell, run az account show --query tenantId -o tsv. The result must match the Tenant ID shown in Tackle. If it doesn’t, switch to the correct directory, copy the command again, and re-run it.
PowerShell instead of Bash
Switch Cloud Shell to Bash, copy the command again, and re-run it. Then select Launch Cloud Shell in Tackle again so Tackle starts listening for the connection.
Stale or truncated command
Refresh the page, copy the command again, and paste the full line into Cloud Shell.
Connection still shows Action Required
Copy the command again and re-run it. Then select Launch Cloud Shell in Tackle and wait the full 5 minutes.
“Tackle does not have this Azure application ID”
Contact [email protected] with the error text and a screenshot of the Microsoft tile.
Cloud Shell subscription error
Follow the steps in Connect to Microsoft to create a subscription, then return to Cloud Shell and try again.