Microsoft Azure NetworkExperiments

What authentication does the Azure Network Experiments API use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential.

Can I run an A/B latency experiment between two endpoints through this API?

Yes. After creating a NetworkExperiment Profile, PUT under /providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName} creates an A/B experiment that defines control and treatment endpoints. Real client measurements accumulate over the experiment duration and are exposed via the LatencyScorecard and Timeseries subresources.

What are the rate limits for the Azure Network Experiments API?

The control plane follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. Latency scorecard and time series reads are inexpensive but should be cached for at least one hour, since the underlying real-user data updates on a slow cadence.

How do I retrieve a latency scorecard through Jentic?

Search Jentic for get azure network experiment latency scorecard, load the schema for GET .../Experiments/{experimentName}/LatencyScorecard, and execute it with the profile and experiment names. Jentic handles AAD token exchange and returns the scorecard JSON, which the agent can then summarise for stakeholders.

Does the API run synthetic probes or use real user measurements?

Azure Internet Analyzer uses real-user measurements collected through a JavaScript snippet in customer web pages, not synthetic probes. The experiment results therefore reflect the latency seen by the actual visitor population, which is the property that drives the API's value over synthetic monitoring.

Can I limit what my agent is allowed to do with the Azure Network Experiments API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. Every operation carries the subscription id, resource group, and profile name in its path, so you can pin the agent to a single NetworkExperiment Profile in one resource group. You also choose the operations it may call, so you can allow read-only access to latency scorecards and time series while excluding writes such as creating or updating a profile or experiment.