Create a Resource Group

1. From the Azure services section, on the Azure portal home page, click on Resource groups to open the resource groups page.

Open

2. Click Create from the Resource groups toolbar.

Open

3. Enter the following resource group details on the Create a Resource group page:

4. Click Review + Create to validate and create new resource groups.

5. Click Next: Tags > to navigate to the next screen. Please skip entering any tags as they aren’t required.

6. Click Review + Create to validate and create new Resource groups successfully. The Validation passed message is displayed if validation passes successfully.

7. When validation passes successfully, click Create to add new Resource groups.

Deploying CAM Azure Stack to the Azure Subscription

1. Using a browser, navigate to the CAM Azure Stack GitHub repository using the URL GitHub - Prosperoware/cam-azure-deployment -

2. Navigate to the repository home page and click on the Deploy to Azure button as the image shows in this section.

3. The link redirects you to the MS Azure Portal and displays the CAM Azure Stack deployment form.

4. Click the Deploy to Azure button. Log into the Azure user portal. The Custom Deployment screen is displayed.

Open

Open

4. Enter the following project details for your Azure deployment:

5. For additional VNet settings based on the part of the stack (MySQL, Cosmos) visit the following section for the vnet security setup:

• Azure Client Stack Deployment | MySQL Server

• Azure Client Stack Deployment | Cosmos

6. Click Review + Create - Validates and create the template if the validation passes as displayed in the following screen.

7. If the form is valid, then the message Validation passed will be displayed. Now, click the Create button to start the deployment process.

Open

1. Click Previous to navigate to the previous screen.

2. The deployment process takes a few minutes to complete. The resources are created one after the other.

Open

3. Once the deployment is completed successfully, you can see the following screen.

Open

Flexible Server from Single Server Configuration

These steps are used to convert a single server deployment to the flexible server as designated by Azure.

1. Follow the Microsoft tutorial steps. Tutorial: Migrate Azure Database for MySQL - Single Server to Flexible Server online using DMS via the Azure portal - Azure Database Migration Service | Microsoft Learn

Those steps we need to do are:

a. Update the compute tier to General Purpose from Burstable S2 by:

b. Go to the MySQL Resource in the Resource Group in Azure.

c. Open Overview.

Open

Open

c. Click On Configuration.

Open

d. Pick Compute Tier General Purpose. Pick Compute Size Standard_D2ads_v5 if staying on the Standard tier.

e. Finish the wizard upgrade.

Update the server configuration within the CAM config yml file next.

1. Go to Storage account container.

2. Find application config container (<instanceUniqueName-topLevelDomain>-application-config eg:tenantname-io-application-config).

3. Go to yml folder.

4. Update 3 attributes (host, username, password) with the new flexible server configuration in appconfig yml (appconfig-<environmentStage>.yml) which is in the yml folder.

Note: Single server username format is username@servername eg: abc@mysql-clientname-io

Flexible Server FAQs

1. Why do I need to create a new resource for flexible server and migrate the data?
   Azure Database for MySQL - Single Server is on the retirement path and is scheduled for retirement by September 16, 2024. For more details see this article: What's happening to Azure Database for MySQL single server?

2. How is the connection established to this sql instance?
   CAM Azure functions connect to this SQL instance using the connection string stored in the YML config file.

3. I can’t find any relevant config in the account?
   In the storage account, there should be a bucket with a name ending with “-application-config”, in that bucket, there should be a file with a name that follows the convention “appconfig-<environmentStage>.yml”, that is the file they need to update.

Initialize CAM Azure Stack Configuration

1. After the deployment is completed successfully, CAM Azure Stack needs to be initialized. The initialization URL is in the template deployment output.

2. Click Outputs, from the template deployment page left panel.

3. The following screen is displayed. Copy the initializeFunctionUrl and paste it into your Internet browser’s URL address bar.

Open

4. The initialization function process URL will respond with the initialization status in JSON format. A successful response looks like the following:

Open

5. Display the bucketname.

6. Display the apiEndPointBaseUrl.

Configure CAM Content Mover to Utilize your Azure Stack

1. The below steps can be done for Content Mover or Data Sync (Content Sync).

2. Navigate to your CAM instance, click Administration > click Content Mover. The following screen appears:

Open

3. Navigate to the Configuration tab, the following screen appears:

Open

4. Click Save to save the configuration.

5. Click Cancel to close the configuration screen without saving any changes to the fields.

6. If using Data Sync, repeat the above steps but after clicking Administration- Data Sync

Configure CAM Data Sync to Utilize your Azure Stack

1. The below steps can be done for Content Mover or Data Sync (Content Sync).

2. Navigate to your CAM instance, click Administration >> click Data Sync, and the following screen appears.

Open

3. Navigate to the Content Sync Settings tab, and the following screen appears:

Open

4. Click Save to save the configuration.

5. Click Cancel to close the configuration screen.

Optional Azure Resources Configurations

Deployment Errors, Workarounds, and Solutions

In this section, we are going to document:

• The errors that occur while deploying Content Mover on the Azure Stack.

• Workarounds/solutions on how to handle these errors and scenarios that can occur during deployment

Finding logs and running queries for troubleshooting on MS Azure

On MS Azure, go to the resource group on the left-top corner click on Logs, and select one of the entries. Entries in this list will be tied to one of these: All Queries, Alerts, Browsing Data, Performance, and Reports Failures.   

Open

Workarounds and Solutions for Common Errors

• The estimated cost can be calculated using the pricing calculator provided by Microsoft at Pricing Calculator | Microsoft Azure .

• You can adjust some resources, tiers, and configurations based on their usage, but you should maintain the minimum required configurations as explained in the previous section.

• The image below is an example of the estimated costs using the minimum required resources and settings:

Open

All resources created by CAM Azure Stack will be secured using the Azure standard security. Permission will only be granted to the CAM function apps and other CAM Azure Stack resources in the same resource group. No users, accounts, or external apps will be granted access by default except what the Azure subscription administrator has setup previously (inheritance rules).

The details of permissions are as follows:

Storage account

• Reader and Data Access Role: the role is granted to all CAM function Apps.

  • Storage Account Key Operator Service Role: the role is granted to all CAM function Apps.

  • Storage Blob Data Owner Role: The role is granted to all CAM function Apps.

MySQL Server

• No roles assignments or firewall changes are performed by the CAM Azure Stack. The database should only be accessible by CAM function apps deployed within the same resource group, using the admin username/password created during the deployment process. Configurations to secure the flexible server have changed slightly since the retirement of Single Server instances.

  • To configure security for CAM MySQL flexible servers:

    1. Log in to the Azure Portal.

    2. Select the Azure Database for MySQL flexible server instance dedicated to CAM.

    3. On the Azure Database for MySQL flexible server page, under the Settings heading, select Networking.

    4. If a VNet is available in your subscription and you plan to use a private endpoint for secure connectivity:

       1. Under Public access, ensure the checkbox for "Allow public access to this resource through the internet using public IP address" is unchecked.

       2. For the Connectivity method, select "Private endpoint (VNet Integration)" and configure a private endpoint for secure connectivity within your Virtual Network.

       3. Add your VNet or subnet to the VNet firewall rules to enable access for CAM Azure Function Apps.

    5. If VNet is not available in your subscription or you are not planning to use a private endpoint:

       1. Under Public access, ensure the checkbox for "Allow public access to this resource through the internet using public IP address" is checked.

       2. For the Connectivity method, select "Public access (allowed IP addresses) and Private endpoint".

       3. Under Firewall rules, turn on the setting for “Allow access to Azure services” to enable connectivity for Azure services. Be aware this option allows access from any Azure service, not just those within the same resource group.

    For additional information and guidance, please refer to the following Microsoft Knowledge Articles:

  • Deny Public Network Access

  • Public Network Access

  • Manage firewall rules

• All Other resources: no roles assignment or Firewall changes are done by CAM.

• Allow public access to this Azure resource group through the internet using a public IP address

  • This option allows the firewall to permit connections from specific IP addresses or any Azure service. If Public Access is disabled, the Firewall Rules won't be enforced, and any modifications made to the Firewall will be discarded.
    By choosing above option not all public IPs are allowed. We need to specify some IP and azure service is able to communicate with storage without using VPC
    By uncheck above option, we need to create private endpoints to allow hosts in the selected virtual network to access this server. To ensure successful connections to the server, enable public access with firewall rules or create a private link for the server.

Cosmos

• No roles assignments or firewall changes are performed by the CAM Azure Stack. We can connect to Cosmos server using 2 options

  1. Public access:
     If a VNet is available in your subscription and you plan to use a private endpoint for secure connectivity:
     a. Select “public access“ under networking.

  b. Select "Selected network (VNet Integration)" and configure an endpoint for secure connectivity within your Virtual Network.

  c. Add your VNet or subnet to the VNet firewall rules to enable access for CAM Azure Function Apps.
  If a VNet is not available in your subscription

  • Select “All networks“.

  • Please keep in mind this will allow all networks, including the internet, can access this Azure Cosmos DB account.

  • Private endpoint
    a. Select “private endpoint“ under networking.
    b. Use private endpoints to privately connect to a service or resource. Your private endpoint must be in the same region as your virtual network but can be in a different region from the private link resource that you are connecting to.

  • For additional information

• Public access

• Private access

Additional info:

Except for the CAM Azure Stack function apps, none of the resources in the resource group will be accessed externally. For the MySQL Database, the option to “Allow access to Azure services” is enabled during the deployment process and all other IPs are restricted by default. Even though the function apps will be accessed externally, those will be accessed by CAM instance only. If you plan to restrict the function apps inbound IP’s, the Litera Customer Care team (support@litera.com) can provide the list of IPs that should be whitelisted based on your CAM instance Zone. The current list of IPs can be found at iManage .

For additional security, the data container in the storage account will be encrypted using Microsoft-managed-keys encryption scope. After the template deployment, this encryption scope can be updated to use your managed keys or to use an encryption with a key in the managed HSM as explained in the following MS article (Configure encryption with customer-managed keys stored in Azure Key Vault Managed HSM - Azure Storage ).

Managing Security of the Azure Client Stack

In addition to the strong security provided by MS Azure, Litera strengthens data security by controlling and filtering access to even the virtual private clouds hosted by industry-leading cloud services such as MS Azure. While managing the Azure cloud, customers can also take precautions to detect and prevent suspicious activities. Litera helps you to track and monitor logs, audit system calls, and set up alerts for potential intrusions.

Litera’s systems support the latest secure cypher suites, including TLS 1.2 and later protocols, AES256 encryption, and SHA2 signatures.

Litera ensures the safety of data at rest by encrypting the data using 256-bit Advanced Encryption Standard (AES-256). This standard is applied to relational databases, file stores, database backups, and so on. Litera even safeguards the encryption keys and processes by encrypting them securely.

Litera has successfully completed the SOC 2 Type II audit. The customer's sensitive data remains secure. Litera encourages you to use the private subnets to deploy CAM. For more information, see the FAQs section.

As part of our disaster recovery plan, Litera provides secure-tested backups. Data is backed up automatically and the backups are encrypted and stored securely.