Using azure appinsights with aadb2c

Question

Pulumi · Accepted Answer

To create an Azure Application Insights resource that can be integrated with an Azure AD B2C tenant, you need to follow these steps:

1. Create an instance of Azure Application Insights using the `azure.appinsights.Insights` resource type. This will grant you monitoring and analytics capabilities for any application you choose to connect.
2. Create an Azure AD B2C tenant using the `azure.aadb2c.Directory` resource type. This serves for managing user identities and authentication processes.

Let's assume you've already set up a B2C tenant and you want to enable tracking and diagnostics for applications that authenticate using that B2C tenant. You can send telemetry from your applications to Application Insights, allowing you to monitor the performance, track usage, and diagnose issues with greater ease.

The following TypeScript program demonstrates how you can declare each of these resources using Pulumi:

```typescript
import * as azure from "@pulumi/azure";

const resourceGroupName = "my-resource-group";
const location = "West US";

// Note: Ensure the Pulumi Azure provider is configured to use your credentials.

// Create an Azure AD B2C Tenant
const b2cTenant = new azure.aadb2c.Directory("myB2CTenant", {
    resourceGroupName: resourceGroupName,
    skuName: "Standard", // Choose the appropriate SKU for your project
    displayName: "My B2C Tenant",
    domainName: "myb2ctenant.b2clogin.com",
    countryCode: "US",
    // Ensure this location matches the Application Insights resource location
    dataResidencyLocation: location,
});

// Create an Application Insights resource
const appInsights = new azure.appinsights.Insights("myAppInsights", {
    resourceGroupName: resourceGroupName,
    location: location,
    applicationType: "web", // Choose the appropriate application type
    retentionInDays: 90, // Set the data retention policy as needed
    dailyDataCapInGb: 1, // Set a daily data cap to manage costs
    internetIngestionEnabled: true,
    internetQueryEnabled: true,
});

// Output the Instrumentation Key which you'll use in your applications
export const instrumentationKey = appInsights.instrumentationKey;
```

In the above program:

- Replace `my-resource-group` with the name of your existing Azure resource group.
- Replace `West US` with the region that makes the most sense for your location and compliance needs.
- `skuName`: Specifies the SKU/tier of the Azure AD B2C tenant.
- `displayName`: A friendly name for the Azure AD B2C tenant.
- `domainName`: The initial domain name for the B2C tenant. This is your tenant's identifier on the internet and must be globally unique.
- `countryCode`: The ISO country code, which indicates the country/region of your tenant.

Once you've initialized these resources, use the `instrumentationKey` from the Application Insights resource in your application's telemetry configuration. Any events, traces, or metrics logged from your application will then appear in the Application Insights instance, which you can query or set up alerts and dashboards to monitor.

Remember to replace the placeholders like `myB2CTenant` and `myAppInsights` with names that make sense for your application.

This program is a starting point and you will need to consider the best practices around naming, resource dependencies, and configuration to better fit your specific use case.