• Open an elevated PowerShell command prompt and

• Install the latest AzureRM modulesinstall-module -Name AzureRM (enter y at prompt - you may get an error if modules are already installed.)

• Save the Enable-AzureRMDiagnostics.ps1 script locallysave-script -Name Enable-AzureRMDiagnostics -Path "C:\Temp"

• Change path to c:\temp and execute the script.\Enable-AzureRMDiagnostics.ps1 -ResourceGroup rg-contosouni-gd  (Note - you will need to change this to the name of your resource group that contains the Azure Web App and Azure SQL DB)

• You will need to run through the wizard once and select for the Azure Web App:
  • Subscription
  • Log Analytics Workspace
  • Resource Type ==> Microsoft.Web/sites
• You will need to re-run the script and go through the wizard and select for the Azure SQL DB:
  • Subscription
  • Log Analytics Workspace
  • Resource Type ==> Microsoft.Sql/servers/databases
• Now go to the OMS Solutions Gallery (through the OMS portal) or the Azure market place (through the Azure portal) and add:
  • Azure Web Apps Analytics
  • Azure SQL Analytics

  Azure Web Apps Analytics	Azure SQL Analytics

• In about 15 minutes you should start to get metrics

If you need to onboard PaaS and SaaS resources that are in a different subscription from your log analytics workspace then you can run the script and pass it parameters

• .\Enable-AzureRMDiagnostics.ps1 -WSID "/subscriptions/fd2323a9-2324-4d2a-90f6-7e6c2fe03512/resourceGroups/OI-EAST-USE/providers/Microsoft.OperationalInsights/workspaces/OMSWS" -SubscriptionId "fd2323a9-2324-4d2a-90f6-7e6c2fe03512" -ResourceType "Microsoft.Sql/servers/databases" -ResourceGroup "RGName" -Force

The above command line will take in parameters and execute silently without prompting using Force.

• Unzip the folder and you'll find another folder called C#. Extract this and perhaps change the name to ContosoUni. [gallery size="full" link="file" ids="145"]

• We'll need to create some resources to publish our project into e.g. an Azure SQL Database. You can either create all the resources manually or you can edit this script and change the lines that will be specific for you.

• When the script completes you should see the following resources in Azure:

• Now open the Visual Studio project. You'll be prompted a couple of times; click OK and we'll configure the project to work with Visual Studio 2015.

• Next you will need to edit the Web.config file

• And change v11.0 to MSSQLLocalDB (as below). From <connectionStrings> <add name="SchoolContext" connectionString="Data Source=(LocalDB)\v11.0;Initial Catalog=ContosoUniversity2;Integrated Security=SSPI;" providerName="System.Data.SqlClient" /> </connectionStrings> To: <connectionStrings> <add name="SchoolContext" connectionString="Data Source=(LocalDB)\MSSQLLocalDB;Initial Catalog=ContosoUniversity2;Integrated Security=SSPI;" providerName="System.Data.SqlClient" /> </connectionStrings>

• In Solution Explorer, right click the project and choose Manage NuGet Packages

• A yellow bar will appear stating "Some NuGet packages are missing ..." - click the restore button at the end of this yellow bar

• Save and exit Visual Studio

• Open Visual Studio (Visual Studio needs a restart after restoring the NuGet packages

• On the menu bar, choose Tools, NuGet Package Manager, Package Manager Console

• In the Package Manager Console, enter Update-Database

• Build the solution

• On the menu bar, choose Project, Contoso University Properties, and select the Package/Publish SQL tab

• Change Configuration (top item) to Release

• Click Enable This Page

• Click Import from Web.config

• In the text box for Connection String to destination database: click the ellipse button at the end of the empty text box to configure  ...

• Enter the details for the Azure SQL Database that we created with the PowerShell script (or which you created in some other way).

• Change the Database Scripting Options to Schema and Data

• Save and Build

• Publish to Azure

• Select Microsoft Azure App Service

• Select your Subscription

• Select the Resource Group

• Select the Web App

• Click OK

• On the Publish window that pops up, you are on the Connection tab - click Validate Connection

• On the Publish window select the Settings tab and ensure that:
  • Configuration states Release
  • File Publish Options (leave deselected)
  • Database - Enable the new database publishing improvements
  • Re-enter the connection details to the Azure SQL DB as listed above
  • Check both items under this:
    • Use this connection string at runtime
    • Execute Code First Migrations
  • Click Publish

• You should now see the website with some data populated

• In the next article, I'll look at monitoring this with Operations Management Suite using the Azure Metrics that are in Public Preview

• Configuring a web application that uses a database backend (An Azure Web App with Azure SQL Database)
• Configuring PaaS and SaaS Monitoring from Operations Management Suite
• Integrating the monitoring with Power BI for even richer visualisations
• Configuring Application Insights monitoring and integrating with the Operations Management Suite