Azure.Provisioning.ApplicationInsights 0.1.0

Azure Provisioning client library for .NET

Azure.Provisioning.ApplicationInsights simplifies declarative resource provisioning in .NET for Azure Application Insights.

Getting started

Install the package

Install the client library for .NET with NuGet:

dotnet add package Azure.Provisioning.ApplicationInsights

Prerequisites

You must have an Azure subscription.

Authenticate the Client

Key concepts

This library allows you to specify your infrastructure in a declarative style using dotnet. You can then use azd to deploy your infrastructure to Azure diretly without needing to write or maintain bicep or arm templates.

Examples

Here is a simple example which creates a KeyVault.

First create your Infrastructure class.

public class SampleInfrastructure : Infrastructure
{
}

Next add your resources into your infrastructure and then Build.

// Create a new infrastructure
var infrastructure = new SampleInfrastructure();

// Add a new key vault
var keyVault = infrastructure.AddKeyVault();

// You can call Build to convert the infrastructure into bicep files
infrastructure.Build();

Troubleshooting

• File an issue via GitHub Issues.
• Check previous questions or ask new ones on Stack Overflow using Azure and .NET tags.

Next steps

Contributing

For details on contributing to this repository, see the contributing guide.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (for example, label, comment). Follow the instructions provided by the bot. You'll only need to do this action once across all repositories using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any other questions or comments.