Page Comparison

• Log into the Azure portal and search for the SQL Servers option
• Select Create
• Select a previously created Subscription and Resource Group
• Set the name for the Server and its location
• Set Authentication method to either "Use SQL authentication" or "Use both SQL and Azure AD authentication"
  • NOTE: SQL Server Authentication is the only authentication method needed, but Azure AD authentication provides a more secure way to externally connecting to the databases.

• Set the SQL Server admin login and Password

• Go to Next: Networking
• Set Allow Azure services and resources to access this server to Yes

• Click Next: Additional settings
• Set Enable Microsoft Defender for SQL to Not now

• Click Next: Tags
• Set any desired Tag name and its values

• Go to Review + create

• Review the generated configuration 
• Click on Create
• You should get a notification regarding your ongoing resource deployment, as well as a redirect to the Deployment Status page

• After the deployment is successful, select "Go to resource" or navigate manually to the created SQL server

We have two options for deploying databases, either the databases can be pushed to an Azure storage account from SSMS or they can be published directly from SSMS

• Click on Next
• Review the summary and click Finish to deploy the Database
• Repeat the previous 11 steps (32 - 42) with the other 2 databases.

• Open up the EdFi.sln file in the Ed-Fi-Ods-Implementation/application/EdFi.sln file in Visual Studio. You should sign into visual studio using the same credentials that have access to the Azure Portal.
• Right-click on the "Entry Points" → Edfi.Ods.WebApi folder and select "deploy"
• On the deployment screen that comes up select the green plus sign to build a new deployment

• 
  

  Deck
  id web app deploy options
  Card default true id AzureOption1 label Deploy Direct to Azure title Option1 Option 1- deploy straight to Azure Select a target of "Azure" select a specific target of "Azure App Service Windows" choose the appropriate Resource Group and region Choose the App Service that you created the WebApi and "save" Change the target Runtime from Portable to "win-x64" Click Publish. Card id Option2 label Deploy to Azure-ready .zip binary Option 2 - build a portable zip file Select a target of "Folder" Choose a file location Change the target Runtime from Portable to "win-x64" Click Publish. Open up the folder that you deployed to is located and zip up the contents of the deploy directory, not including the directory, with the following PowerShell commands: Code Block language powershell $compress = @{ Path = "WebApi\*" CompressionLevel = "Fastest" DestinationPath = "WebApi.zip"} Compress-Archive @compress This should make a WebApi.zip file. In the Portal, Navigate to the Web Api App Service Plan. On the sidebar search box look for Advanced Tools, click on it and then click Go You’ll be redirected to a service named Kudu. Locate Tools and click Zip Push Deploy Drag and drop the .zip file and wait until it is uploaded, decompressed and deployed

  
  

• Repeat for the Swagger application

• Copy the AdminApp web application folder (usually c:\inetpub\ed-fi\AdminApp) to a working directory.
• Edit the web.config and set stdoutLogEnabled="true". Check what log4netconfig file that appsettings.json is pointing to and in that file make sure that all of the logging files are NOT going to $program_data or something like that. I use ./logs directory
• Open the working directory in PowerShell.
• Zip up the contents of the admin app folder, but do not include the folder itself. In PowerShell the following commands to this:

$compress = @{
  Path = "AdminApp\*"
  CompressionLevel = "Fastest"
  DestinationPath = "AdminApp.zip"}

Compress-Archive @compress

• This should make an “AdminApp.zip” file.
• Log into Azure from the command line with the command;

	  az login

• If you get an SSL error in your browser, put this command in the address bar  “chrome://net-internals/#hsts” and delete the localhost security policy.
• Send it up. The “--src” tag should have the name of the zip file, “-g” is the name of the resource group, and “-n” is the name of the App Service that was created on the portal : 

   az functionapp deployment source config-zip -g customer-success -n AdminAppYsGeorgiaCstEdfi--src AdminApp.zip