From f93f263eff7b05547a357db03b9b422d5c586b79 Mon Sep 17 00:00:00 2001
From: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
Date: Fri, 11 Nov 2022 14:51:37 -0600
Subject: [PATCH] Added custom provider annotation details

Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
---
 docs/features/software-catalog/external-integrations.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/features/software-catalog/external-integrations.md b/docs/features/software-catalog/external-integrations.md
index 65f97fb8da..f3387d31f0 100644
--- a/docs/features/software-catalog/external-integrations.md
+++ b/docs/features/software-catalog/external-integrations.md
@@ -159,7 +159,12 @@ Check out the numbered markings - let's go through them one by one.
    the outcome of that. This example issues a `fetch` to the right service and
    issues a full refresh of its entity bucket based on that.
 5. The method translates the foreign data model to the native `Entity` form, as
-   expected by the catalog.
+   expected by the catalog. Make sure that in this method you include the
+   `backstage.io/managed-by-location` and `backstage.io/managed-by-origin-location`
+   annotations on your `Entity`. If these are not present they will not show up
+   in the Catalog and you will see warnings in your logs. The
+   [Well-known Annotations](./well-known-annotations.md#backstageiomanaged-by-location)
+   documentation has guidance on what values to use for these.
 6. Finally, we issue a "mutation" to the catalog. This persists the entities in
    our own bucket, along with an optional `locationKey` that's used for conflict
    checks. But this is a bigger topic - mutations warrant their own explanatory