Step 5: Agents
Select the Monitoring and Logging agents that should be included in the installation package. The Portal writes the selected agents and their settings into the package that you download later.
Example of the current Portal Agents step in the environment wizard.
Open the Agents Tab
Example of the Agents tab before agent selections are made for the installation package.
Select and expand agents first
Begin by selecting the server and then expanding each agent card that will be part of the package.
Use this sequence:
- Filter and find the relevant agent.
- Expand the agent card.
- Enter base values in displayed order: Server, Port, Service domain, Service account.
- Continue with optional sections shown for that specific agent.
Different agents expose different sections. The runtime and agent capability decide which settings appear.
.NET 10 agents with gMSA support
For .NET 10 agents that support gMSA, configure the base fields first and then review identity-specific toggles.
Typical fields you must review:
- Server
- Port
- Service domain
- Service account
- Advanced identity
- Use preview version
- Use gMSA
- Auto-generate certificate
If Use gMSA is enabled, make sure your account and domain prerequisites are already met. See gMSA accounts.
Example of expanded agent cards where identity options, including gMSA-dependent settings, are available for selected agents.
.NET 10 agents without gMSA support
Some .NET 10 agents do not expose gMSA, but they can still require an agent database.
Enter settings in visible order:
- Base fields: Server, Port, Service domain, Service account
- Optional identity section, if shown
- Database-specific section, when available: Database type, agent database connection string, and prompt for connection string during install
Use the database prompt option when the connection string should be provided during installation runtime instead of stored in the environment definition.
For connection string format, permissions, and deployment patterns, use Agent Database.
Example of an agent configuration entry with agent-database fields, including database type and connection-string behavior.
.NET Framework 4.8 agents
For agents running on .NET Framework 4.8, the same base pattern applies, but gMSA and database options depend on the selected agent implementation.
Use this checklist for each .NET Framework 4.8 agent card:
- Enter base host and identity values first.
- Check whether gMSA is shown and configure it only when available.
- Check whether database settings are shown and configure them only when available.
When a database section is available, follow Agent Database for rights, SQL connectivity, and update behavior.
When gMSA is available, follow gMSA accounts before generating the package.
Example of the agent-card layout used for legacy runtime variants, where only the fields supported by that selected agent are shown.
What to configure for all variations
- Select each required agent.
- Assign a unique port for every selected agent.
- Provide only the settings shown for that agent variation.
- Keep settings consistent with Step 4: Servers service identity decisions.
Important Notes
- The MCP Endpoint is mandatory from v7.4.0 onwards.
- Some agents require additional connection details or database configuration.
- Keep the port plan consistent with the rest of the Environment.
- Validate gMSA and database prerequisites before generating the package.