Microsoft Marketplace · Microsoft Entra ID · Azure DevOps

Microsoft setup guide

From your Marketplace purchase to a connected Radianz organization: follow these steps with your buyer and administrators.

Personal and Team: what your plan includes

Personal includes your own AI usage view, error monitoring, up to five selected repositories across the whole Radianz organization and 30 days of history. Personal can connect, discover and select repositories; it does not collect commits or include commit analysis or team activity. Team includes team AI usage, commit collection and analysis, unlimited repositories and 90 days of history. Your subscription sets these features.

Microsoft bills the license quantity purchased in Microsoft. Assigning a seat or changing active developers in Radianz does not change that purchased quantity. Website trials and launch discounts do not automatically apply to Marketplace; review the terms shown at Microsoft checkout.

Microsoft handles authentication to your Microsoft account. If your Radianz organization requires two-factor authentication, complete the usual Radianz setup or verification after Microsoft sign-in. A Microsoft sign-in does not bypass that requirement.

1. Choose your Microsoft organization

Use your organization's Microsoft Entra directory and work accounts for this setup. You need a buyer with Marketplace purchasing rights and a Radianz organization administrator. Directory search is optional and requires tenant administrator consent. One person can hold several roles.

Follow Microsoft's tenant creation instructions if your organization needs an Entra directory. Use the same customer directory for the purchase and Radianz administrator. Personal is a Radianz product plan, not a requirement to use a personal Microsoft identity. Contact support before purchasing for another organization or through a reseller.

2. Subscribe through Microsoft Marketplace

As the buyer, open the Radianz offer supplied to you in Microsoft Marketplace or Azure portal. Select the plan and license quantity. Review the directory, Azure subscription, resource group, price, term and renewal settings before completing the purchase. Availability depends on your tenant and region.

Choose Configure account on the purchased SaaS subscription to continue in Radianz. To resume later, use this purchase's configuration link; a normal Radianz sign-in does not finish linking the purchase.

3. Link the purchase to Radianz

If you will administer Radianz yourself, follow the account setup shown after Configure account. If a colleague will administer it, that colleague opens Prepare administration, signs in or creates their Radianz organization, links their Microsoft work account when requested, and shares the request code directly with the buyer.

The buyer enters the code from the purchase's configuration flow and checks the administrator and organization before approving. The request code lasts 24 hours; buyer approval lasts one hour. The administrator then reviews and accepts activation. Confirm the subscription is active on Microsoft licenses before assigning seats. No invitation is sent automatically. A support session cannot approve activation on the customer's behalf.

4. Give people access and licenses

As the Radianz administrator, use Users and access for existing members or invitations, then assign available seats in Microsoft licenses. Microsoft directory is an optional shortcut: when available, a tenant administrator can approve read access, search for an eligible enabled member, choose Give access and optionally link an existing developer. Guests and external or disabled accounts are not eligible for this directory shortcut.

Directory access is read-only and lasts at most 10 minutes. Giving access creates an account only in Radianz; it does not create a Microsoft user or automatically send an invitation. Accounts, developer profiles, Git author associations and licenses are separate: link them deliberately. If all licenses are used, access can be created without a license; paid developer features stay off.

5. Connect Azure DevOps, if needed

In Connections, choose Connect Azure DevOps with the Radianz application. Give the displayed application and directory identifiers to your administrators. In that customer directory, search Entra ID → Enterprise applications by application (client) ID. If missing, a tenant administrator creates its local service principal using the Microsoft instructions linked below. Do not register a replacement app or supply a customer secret. Verify that Azure DevOps uses the same directory. When adding the app in Organization settings → Users, use the enterprise application’s service principal object ID, not the app registration object ID.

Grant Basic access and read permission only for the projects and repositories Radianz should collect. Basic may add an Azure DevOps charge. Radianz uses its own application credentials; no personal access token is needed. Verify access, review visible repositories, authorize and connect. Use Manage repositories to exclude repositories from future collection. The verification list checks access; it is not a repository selection.

6. Verify the first collection

Allow regular synchronization to discover repositories, then use Connections → Manage repositories to review selection. Newly discovered repositories start selected. Personal permits five selected repositories across all supported connections: exclude repositories until no more than five remain. Personal discovery does not collect commits. Team commit collection also requires its Commit Analysis module, applicable developer licenses and author associations. In Developers, associate Git authors with the correct developer and licensed account.

For Personal, verify your own AI usage and error monitoring. For Team, an administrator can view Developer activity without consuming a seat for administration; tracking their own work requires a license. Choose dates with a known commit and compare its repository, author and changed files with DevOps. Excluding a repository stops future collection and keeps history; an in-progress collection may finish.

If something is missing

Purchase not linked or still pending
Resume Configure account from the same Azure SaaS purchase. Check the buyer's and administrator's directory and both approval steps. Review the subscription status in Microsoft licenses.
No license available or member cannot sign in
Free an assigned license or increase the purchased quantity in Microsoft, then assign it in Radianz. Check organization membership and the Microsoft sign-in account. Administrator access and paid developer access have separate requirements.
No repositories or commits
Check connection access and repository selection first. For Personal, commit analysis and team activity are not included. For Team commits, also check modules, developer licenses, author associations and dates. Discovery alone does not prove collection finished. Use Check access if permissions changed.
Directory search disconnected
Reconnect from Microsoft licenses when the temporary session expires. Disconnecting directory search does not remove existing Radianz members or their licenses.

Management links require an authorized signed-in administrator and enabled features. This guide is available before sign-in.

Other getting started guides