Merge pull request MicrosoftDocs#85725 from apfoerts/apfoerts-patch-1

PRMerger15 · web-flow · commit d727532fa8be · 2019-08-16T16:35:48.000-07:00
CreateUiDefinition Updates
diff --git a/articles/managed-applications/create-uidefinition-overview.md b/articles/managed-applications/create-uidefinition-overview.md
@@ -48,14 +48,12 @@ The schema of the parameters property depends on the combination of the specifie
 
 Including `$schema` is recommended, but optional. If specified, the value for `version` must match the version within the `$schema` URI.
 
-You can use a JSON editor to create your UI definition then test it in the [UI Definition Sandbox](https://portal.azure.com/?feature.customPortal=false&#blade/Microsoft_Azure_CreateUIDef/SandboxBlade) to preview it. For more information about the sandbox, see [Test your portal interface for Azure Managed Applications](test-createuidefinition.md).
+You can use a JSON editor to create your createUiDefinition then test it in the [createUiDefinition Sandbox](https://portal.azure.com/?feature.customPortal=false&#blade/Microsoft_Azure_CreateUIDef/SandboxBlade) to preview it. For more information about the sandbox, see [Test your portal interface for Azure Managed Applications](test-createuidefinition.md).
 
 ## Basics
 
 Basics is the first step generated when the Azure portal parses the file. In addition to displaying the elements specified in `basics`, the portal injects elements for users to choose the subscription, resource group, and location for the deployment. When possible, elements that query deployment-wide parameters, like the name of a cluster or administrator credentials, should go in this step.
 
-If an element's behavior depends on the user's subscription, resource group, or location, then that element can not be used in basics. For example, **Microsoft.Compute.SizeSelector** depends on the user's subscription and location to determine the list of available sizes. Therefore, **Microsoft.Compute.SizeSelector** can only be used in steps. Generally, only elements in the **Microsoft.Common** namespace can be used in basics. Although some elements in other namespaces (like **Microsoft.Compute.Credentials**) that do not depend on the user's context are still allowed.
-
 ## Steps
 
 The steps property can contain zero or more additional steps to display after basics, each of which contains one or more elements. Consider adding steps per role or tier of the application being deployed. For example, add a step for master node inputs, and a step for the worker nodes in a cluster.
diff --git a/articles/managed-applications/request-just-in-time-access.md b/articles/managed-applications/request-just-in-time-access.md
@@ -57,7 +57,7 @@ In "steps":
 In "outputs":
 
 ```json
-"jitAccessPolicy": "[parse(concat('{\"jitAccessEnabled\":', string(steps('jitConfiguration').jitConfigurationControl.jitEnabled), ',\"jitApprovalMode\":\"', steps('jitConfiguration').jitConfigurationControl.jitApprovalMode, '\",\"maximumJitAccessDuration\":\"', steps('jitConfiguration').jitConfigurationControl.maxAccessDuration, '\",\"jitApprovers\":', string(steps('jitConfiguration').jitConfigurationControl.approvers), '}'))]"
+"jitAccessPolicy": "[steps('jitConfiguration').jitConfigurationControl]"
 ```
 
 > [!NOTE]
diff --git a/articles/managed-applications/test-createuidefinition.md b/articles/managed-applications/test-createuidefinition.md
@@ -85,7 +85,7 @@ For Azure CLI, use:
 
 The script opens a new tab in your browser. It displays the portal with your interface for creating the managed application.
 
-Provide values for the fields. When finished, you see the values that are passed to the template.
+Provide values for the fields. When finished, you see the values that are passed to the template which can be found in your browser's developer tools console.
 
 ![Show values](./media/test-createuidefinition/show-json.png)
 
