|
| 1 | +--- |
| 2 | +title: Submit an App Catalog update request |
| 3 | +description: This article provides instructions for app owners and nonapp owners on how to submit an update request for an app in the Defender for Cloud Apps catalog. |
| 4 | +ms.date: 06/30/2025 |
| 5 | +ms.topic: how-to |
| 6 | +--- |
| 7 | + |
| 8 | +# Submit an App Catalog update request |
| 9 | + |
| 10 | +To keep the Microsoft Defender for Cloud Apps (MDA) catalog accurate and secure, use the right submission method based on your relationship to the app and the type of update needed. |
| 11 | + |
| 12 | +## App owners or verified vendors |
| 13 | + |
| 14 | +If you're a verified app vendor or developer, complete the [Self-Attestation Questionnaire](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4CRHM-U7CtKpJma_QJAnSlUMEpLQzBaQ1hWNDMxUEhRNFI3Q0FZUkdWRC4u) to: |
| 15 | + |
| 16 | +- Add a new app to the catalog. |
| 17 | + |
| 18 | +- Update risk attributes. |
| 19 | + |
| 20 | +**While we review your request:** |
| 21 | + |
| 22 | +- If the app isn’t in the catalog, you can [add it as a custom app](cloud-discovery-custom-apps.md) in Cloud Discovery to monitor its usage in your environment. |
| 23 | +- If the app is listed but its risk score doesn’t reflect your organization’s security posture, you can manually [override the app’s risk score](risk-score.md#override-the-risk-score). |
| 24 | + |
| 25 | +## Nonowners requesting updates |
| 26 | + |
| 27 | +Even if you're not the app owner, you can help improve the app catalog's accuracy: |
| 28 | + |
| 29 | +- You can [request a risk score update](risk-score.md#customize-the-risk-score) for apps in use by your organization. |
| 30 | +- You can [suggest a change to the cloud app catalog](risk-score.md#suggest-a-change-to-the-cloud-app-catalog) if you find a new app in your environment that hasn't been scored by Defender for Cloud Apps, or if you want to request a review for a new risk factor, a score update, or outdated app data. |
| 31 | + |
| 32 | +## Validation and processing timeline |
| 33 | + |
| 34 | +We thoroughly validate all catalog update requests to ensure accuracy and relevance. All app catalog requests must meet these criteria: |
| 35 | + |
| 36 | +- The submitted domain must map to a known application. |
| 37 | +- The app must qualify as a SaaS product. |
| 38 | +- The request must include complete and verifiable information. |
| 39 | + |
| 40 | +We typically update the catalog within three weeks of receiving your request. |
| 41 | + |
| 42 | +## All other requests |
| 43 | + |
| 44 | +For general inquiries, metadata corrections, or update requests that don’t fall into the previous categories, [open a support ticket](/defender-cloud-apps/support-and-ts) |
| 45 | + |
| 46 | +> [!NOTE] |
| 47 | +> We review support tickets on a case-by-case basis. They aren’t a fast track for catalog updates but help capture edge cases or routing issues needing broader investigation. |
| 48 | +
|
| 49 | + |
| 50 | +## Related articles |
| 51 | + |
| 52 | +- [Find your cloud app and calculate risk scores](risk-score.md) |
| 53 | +- [Attest your apps](attest-your-app.md) |
| 54 | +- [Add custom apps to cloud discovery](cloud-discovery-custom-apps.md) |
0 commit comments