# Configure Dependencies in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Dependencies** tool is optional.
{% endhint %}
The **Dependencies** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to create dependencies within a deployment, whereby the app being deployed requires one or more other apps to have already been installed on the targeted resource before it can be deployed.
If the required app(s) (known as the *parent*) have not already been installed on the device, they will automatically be installed before the app that is being deployed (known as the *child app*) is installed.
{% hint style="danger" %}
**Important**
Before you can create an App Dependency in a PMPC Cloud deployment, the deployment for the parent app(s) must:
* exist already
* have been deployed successfully
The parent app can be packaged without assignments and used in a Dependency chain rule, provided the parent app is deployed first.
Also, apps that have not been successfully deployed (such as those with a status of **Failed**, **Retrying**, **Processing**, etc.) cannot be used to create an app dependency, nor can apps with **Uninstall** or **Update Only** assignments.
{% endhint %}
{% hint style="info" %}
**Note**
Like Intune, we do not support circular dependencies (i.e. App A has a dependency on App B, and App B has a dependency on App A).
As per Intune, you can create a maximum of 100 dependencies, which includes the dependencies of any included dependencies, as well as the app itself. See [Step 5: Dependencies](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-5-dependencies) of [Add, assign, and monitor a Win32 app in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add) for more information.
Also, the parent app must have been deployed successfully before you can create a dependency between apps.
{% endhint %}
To add a dependency:
1. Add the [**Dependencies** tool](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/..#adding-additional-tools).
{% hint style="info" %}
**Note**
If we are aware that an app requires a dependency, we automatically add the **Dependencies** tool with a yellow dot after the tool name. If you click the **Dependencies** tool, we show you the name of the app we recommend you add as a dependency for this deployment.
{% endhint %}
2. Click the **Dependencies** tool.
3. From the **Add Dependencies** field, either:
1. Start typing the name of the relevant app that this app depends on already being successfully installed on the target device.
2. Click the dropdown and select the relevant app that this app depends on already being successfully installed on the target device.
The selected app appears under the **Parent Deployment** section.
{% hint style="info" %}
**Note**
Click the trashcan beside the relevant app under the **Parent Deployment** section to delete a dependency.
{% endhint %}
4. Repeat Step 3. to add any additional dependencies.
{% hint style="success" %}
**Tip**
Once a dependency has been configured, you can view it as part of the app’s properties in the Microsoft Intune admin center.
For more information, see [Step 5: Dependencies](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-5-dependencies) of [Add, assign, and monitor a Win32 app in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add).
{% endhint %}
{% hint style="info" %}
**Note**
If a dependency is set up in the Intune admin center between an app managed by PMPC Cloud and an app managed directly in Intune, we will always copy-forward any dependencies from the PMPC Cloud app whenever we update the PMPC Cloud app.
{% endhint %}
{% hint style="danger" %}
**Warnings**
If we encounter any problems with app dependencies, we display a yellow exclamation mark (“**!**”) warning. Hovering over this will display more information.
We typically generate warnings in the following scenarios:
* If a dependency fails to be created. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* If a dependency fails to be carried forward. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* When multiple parent dependencies exist, any warnings will specify which particular dependency failed to be created to help you troubleshoot the issue.
If an entire deployment fails before the dependencies stage is reached, no warnings are shown, as we only show warnings for successful deployments.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
We typically generate warnings in the following scenarios:
* If a dependency fails to be created. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* If a dependency fails to be carried forward. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* When multiple parent dependencies exist, any warnings will specify which particular dependency failed to be created to help you troubleshoot the issue.
If an entire deployment fails before the dependencies stage is reached, no warnings are shown, as we only show warnings for successful deployments.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.