Skip to content

Commit 46f7243

Browse files
Merge pull request #207228 from jbyway/patch-4
Update app-attach-azure-portal.md
2 parents b736f6d + 6530ac1 commit 46f7243

File tree

1 file changed

+0
-16
lines changed

1 file changed

+0
-16
lines changed

articles/virtual-desktop/app-attach-azure-portal.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -42,19 +42,6 @@ reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager\De
4242
4343
```
4444

45-
## Configure the MSIX app attach management interface
46-
47-
Next, you'll need to download and configure the the MSIX app attach management interface for the Azure portal.
48-
49-
To set up the management interface:
50-
51-
1. [Open the Azure portal](https://portal.azure.com).
52-
2. If you get a prompt asking if you consider the extension trustworthy, select **Allow**.
53-
54-
> [!div class="mx-imgBorder"]
55-
> ![A screenshot of the untrusted extensions window. "Allow" is highlighted in red.](media/untrusted-extensions.png)
56-
57-
5845
## Add an MSIX image to the host pool
5946

6047
Next you'll need to add the MSIX image to your host pool.
@@ -153,9 +140,6 @@ To publish the apps:
153140

154141
After assigning MSIX apps to an app group, you'll need to grant users access to them. You can assign access by adding users or user groups to an app group with published MSIX applications. Follow the instructions in [Manage app groups with the Azure portal](manage-app-groups.md) to assign your users to an app group.
155142

156-
>[!NOTE]
157-
>MSIX app attach remote apps may disappear from the feed when you test remote apps during public preview. The apps don't appear because the host pool you're using in the evaluation environment is being served by an RD Broker in the production environment. Because the RD Broker in the production environment doesn't register the presence of the MSIX app attach remote apps, the apps won't appear in the feed.
158-
159143
## Change MSIX package state
160144

161145
Next, you'll need to change the MSIX package state to either **Active** or **Inactive**, depending on what you want to do with the package. Active packages are packages your users can interact with once they're published. Inactive packages are ignored by Azure Virtual Desktop, so your users can't interact with the apps inside.

0 commit comments

Comments
 (0)