There was a requirement to automate the creation of DNS entries while provisioning the new service in the Azure. I have used C#. net, JavaScript and SQLite DB for this development. The C# app is responsible to create the DNS entries using WMI queries on MicrosoftDNS and Azure DNS servers. The SQLite DB is used to hold the authorization information, server details, dns entries, user tokens, etc. There is an admin portal which is using cshtml and JavaScript for admin operations.

Azure Automation:

i. Securing the nodes in Virtual Machine Scale Set of the Service Fabric with the desired TLS versions enabled
ii. Securing the App Services by enabing TLS and SSL for secure communication
iii. Managing the Azure AD accounts by creating/updating users to them
iv. Monitoring the Azure resources by enabling Azure metrics on them and setting alerts against threshold
v. Managing the artifacts by pushing them to the Blob storage and deleting the blob content after some specific time
vi. Cleanup of the deployment history using Azure Automation Accounts
vii. Setting up the KeyVault policies
viii. Encrypting sensitive values and pushing them to the Key Vaults
ix. Pushing the required app settings to the App Services and Staging Slots
x. Securing the SQL Server with the Audit and Threat Policy
xi. Starting, stopping the App Services and Staging Slots
xii. Creating the Azure Container Instances
xiii. Setting up the tagging for all Azure resources
xiv. Cert rotation for Azure App Services, Service Fabrics
xv. Multiple Excel reports based on sizes of the resources, costing of the resources
xvi. Automated resource group creation on Azure without needing to wait for approvals for developers on Sandbox subscription

Octopus scripts:

i. Moving the step templates between the Octopus servers
ii. Moving the library sets between the Octopus servers
iii. Asserting the resource groups on Azure using Octopus
iv. Add events to SEQ when Octopus deployment finishes or fails
v. ARM templates security scan to check if we are using ARM templates which are secure
vi. Adding specific steps to the projects if not present already
vii. AzureRM to Az modules migration

I have provisioned the infrastructures for SAAS apps (Cloud Native Applications).
The decision of using ARM templates was made to automate the infrastructures for the services in
different environments like Sandbox, Development, Performance Testing, QA and Production.

Octopus is the automation tool being used in Bentley. I have worked on project provisioning and deployed those to the different environments. Octopus has the various capabilites to share the same step templates and variables, scoping the variables according to environments, cloning different projects. Has the ability to perform operations using UI and APIs, it means whatever you can do using UI can be done using APIs. Has the ability to manage the accesses by creating the Teams. You can audit each and every activity.

Worked on migration of the code from TFS to Azure DevOps.
Managed multiple build and release pipelines, set the standards in these pipelines so that all teams can use these to automate the deployment of their service.
Enabled the build pipelines for the continuous integration (CI) based on the Pull Requests (PR).
Enabled the release pipelines for the continuous deployment (CD) based on the latest build happens.
Integrated the Octopus related tasks in the release pipelines for the deployments in different environments.
Integrated the Security tasks and ScoreCard tasks to validate if the service is in good state to deploye in all aspects.

There was a requirement to automate the creation of DNS entries while provisioning the new service in the Azure. I have used C#. net, JavaScript and SQLite DB for this development. The C# app is responsible to create the DNS entries using WMI queries on MicrosoftDNS and Azure DNS servers. The SQLite DB is used to hold the authorization information, server details, dns entries, user tokens, etc. There is an admin portal which is using cshtml and JavaScript for admin operations.

There was the manual process to provision the service, and there was a SharePoint form to do this. The access to provision everything was being handled by multiple teams and developers didnt have much flexibility there. I have contributed in this project to develop an app which will provide the flexibility to the developers to do the things on their own. This app has multiple modules - admin, form approvers, form creaters. This app is developed using Dot net core MVC, Reactjs for UI components, Azure SQL for holding authorization information, form data coming from UI, App Insights for collecting the logs from app, SEQ to store the traces and events from app.

There are bunch of PowerShell scripts I developed, but few important ones I have mentioned below: Azure automation: i. Securing the nodes in Virtual Machine Scale Set of the Service Fabric with the desired TLS versions enabled ii. Securing the App Services by enabing TLS and SSL for secure communication iii. Managing the Azure AD accounts by creating/updating users to them iv. Monitoring the Azure resources by enabling Azure metrics on them and setting alerts against threshold v. Managing the artifacts by pushing them to the Blob storage and deleting the blob content after some specific time vi. Cleanup of the deployment history using Azure Automation Accounts vii. Setting up the KeyVault policies viii. Encrypting sensitive values and pushing them to the Key Vaults ix. Pushing the required app settings to the App Services and Staging Slots x. Securing the SQL Server with the Audit and Threat Policy xi. Starting, stopping the App Services and Staging Slots xii. Creating the Azure Container Instances xiii. Setting up the tagging for all Azure resources xiv. Cert rotation for Azure App Services, Service Fabrics xv. Multiple Excel reports based on sizes of the resources, costing of the resources xvi. Automated resource group creation on Azure without needing to wait for approvals for developers on Sandbox subscription Octopus scripts: i. Moving the step templates between the Octopus servers ii. Moving the library sets between the Octopus servers iii. Asserting the resource groups on Azure using Octopus iv. Add events to SEQ when Octopus deployment finishes or fails v. ARM templates security scan to check if we are using ARM templates which are secure vi. Adding specific steps to the projects if not present already vii. AzureRM to Az modules migration