---
title: "Cloud Print Connector: Data Refresh Best Practices"
slug: "cloud-print-connector-data-refresh-best-practices"
description: "These are the best practices to follow for Lasernet Cloud Print Connector settings after an FO database refresh from Production to a Sandbox environment."
updated: 2025-05-01T14:19:21Z
published: 2025-05-01T14:19:21Z
canonical: "kb.lasernetgroup.com/cloud-print-connector-data-refresh-best-practices"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud Print Connector: Data Refresh Best Practices

This page explores the best practices to follow for Lasernet Cloud Print Connector settings after a Dynamics 365 Finance and Operations database refresh from Production to a Sandbox environment.

Note

The following steps all occur in SandBox. No changes are made in Production.

#### Prerequisites

You must have separate and valid Azure Service Buses and Azure storages for Sandbox and Production cloud printing. These can be found in **Lasernet** > **Setup** > **Administration** > **Connection**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-RPSJR5B4.png)

1. In Sandbox, export the Lasernet backup with **Lasernet Azure parameters** and **Azure On-premises user mapping**.
2. Navigate to **Lasernet** > **Common** > **Backup** > **Export Lasernet Backup**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-3M9CI870.png)

1. Select the **Endpoint type** from the dropdown.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-G04447SG.png)

1. Ensure that **Lasernet Azure parameters** and **Azure On-premises user mapping** are selected.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-3OISSZP5.png)

#### Steps in Sandbox Environment

After a DB refresh from Production to Sandbox:

1. Navigate to **Lasernet** > **Setup** > **Cloud print connector setup** > **User setup**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-SZ59G8BX.png)

1. Click **Delete locally** on the Azure User mapping for Production’s cloud printing. This will delete the mapping details in the Sandbox environment but will not affect the queue in Azure or Production.

Warning

Do not click **Delete**, as this will remove the Azure user mapping in Azure.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-4KXZKH6F.png)

1. Navigate to **Lasernet** > **Setup** > **Cloud print connector setup** > **Parameters** and replace the **Azure Storage Connection-string** connection (A) with the Sandbox environment's Azure connection string connection.
2. Click **Validate connection string** (B).

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-8GGZEU7G.png)

1. Replace the **Azure Service Bus Connection-string** connection (A) with the Sandbox environment's Azure Service Bus connection string connection.
2. Click **Validate Service Bus Connection String** (B).

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-CH5A5MT0.png)

The Sandbox cloud parameters are no longer connected to the Production Azure storage and Azure Service Bus for cloud printing.

1. Clean up the printer list in Sandbox by navigating to **Lasernet** > **Setup** > **Lists** > **Printers**. Select all the cloud printers and click **Delete** on the top menu. These printers are associated with the Production Azure storage and Azure Service Bus.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-ZL9ORWEA.png)

1. To bring back the Sandbox cloud printing setups, import the Lasernet backup from Sandbox from the prerequisites section.
2. To update the printer list, navigate to **Lasernet** > **Setup** > **Lists** > **Printers** and click **Download Lasernet Cloud printers**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-YL3PHN8F.png)

1. On the dialog that pops up, click **All** from the **All/User** field and click **Ok**.

> [!NOTE]
> Note
> 
> If the printer list does not update with the cloud printers for Sandbox, enable **Keep last printer info in Azure** on the **Download Lasernet Cloud Printers** dialog. This will delete all data in Azure except for the newest printer information for each Cloud Print Connector ID.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-SO35HQEP.png)

1. Now, the cloud print settings and printers have been updated in Sandbox.

#### Important notes

**Revoke**: This option revokes the Azure permissions for the selected record, making the connection strings in the previously downloaded CPC configuration useless. Do not select Revoke twice consecutively. This will result in the queue being deleted in Azure.

**Reinstate**: This option re-applies the Azure permissions.

**Delete**: This option attempts to delete the queues/blobs in Azure associated with the selected record. It is followed by a local delete (when Azure delete was successful), or simply marking the record as deleted (when Azure delete was unsuccessful).

**Delete locally**: This option was added in Lasernet FO Connector 6.1.0.3, and it deletes the record in the current environment, without impacting anything in Azure or any other Dynamics 365 Finance and Operations environment.