Note limit for Include parameter

Author: DCtheGeek

articles/governance/resource-graph/samples/advanced.md

@@ -1,7 +1,7 @@
 ---
 title: Advanced query samples
 description: Use Azure Resource Graph to run some advanced queries, including working with columns, listing tags used, and matching resources with regular expressions.
-ms.date: 12/05/2019
+ms.date: 03/20/2020
 ms.topic: sample
 ---
 # Advanced Resource Graph query samples
@@ -519,12 +519,18 @@ az graph query -q "limit 1" --include displayNames
 Search-AzGraph -Query "limit 1" -Include DisplayNames
 ```
 
+An alternative to getting the subscription name is to use the `join` operator and connect to the
+**ResourceContainers** table and the `Microsoft.Resources/subscriptions` type. `join` works in Azure
+CLI, Azure PowerShell, portal, and all supported SDK. For an example, see
+[Sample - Key vault with subscription name](#join).
+
 > [!NOTE]
 > If the query doesn't use **project** to specify the returned properties,
 > **subscriptionDisplayName** and **tenantDisplayName** are automatically included in the results.
 > If the query does use **project**, each of the _DisplayName_ fields must be explicitly included in
 > the **project** or they won't be returned in the results, even when the **Include** parameter is
-> used.
+> used. The **Include** parameter doesn't work with
+> [tables](../concepts/query-language.md#resource-graph-tables).
 
 ## Next steps