Microsoft Defender for Cloud Apps
Cloud and workloads

Submit an App Catalog update request

In brief

The page now has clearer section titles and anchors, updated metadata, and more precise wording about when to open a support ticket and how such tickets are reviewed.

What Defender admins need to know

Administrators can use the revised headings and guidance to route catalog update requests more accurately; no action is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Submit an App Catalog update request

To keep the Microsoft Defender for Cloud Apps (MDA) catalog accurate, use the submission method that fits your role and the type of update you need. App owners can submit updates through a self-attestation questionnaire, while other users can request risk score changes or suggest catalog corrections. This article explains each submission path and what to expect during processing.

App ownersSubmit updates as an app owner or verified vendorsvendor

If you're a verified app vendor or developer, complete the Self-Attestation Questionnaire to:

  • If the app isn’t in the catalog, you can add it as a custom app in Cloud Discovery to monitor its usage in your environment.
  • 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.

Nonowners requestingRequest updates as a nonowner

Even if you're not the app owner, you can help improve the app catalog's accuracy:

After we validate and accept your request, the standard turnaround time for a catalog update is approximately seven weeks.

AllSubmit other catalog update requests

For general inquiries, metadata corrections, or update requests that don’t fall into the previous categories,other than self-attestation submissions or risk score updates, open a support ticket.

Related articles