Update app-attach-azure-portal.md

Removing remnants of docs that referred to preview stage notes.

Author: jbyway

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

@@ -46,15 +46,6 @@ reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager\De
 
 Next, you'll need to download and configure the the MSIX app attach management interface for the Azure portal.
 
-To set up the management interface:
-
-1. [Open the Azure portal](https://portal.azure.com).
-2. If you get a prompt asking if you consider the extension trustworthy, select **Allow**.
-
-      > [!div class="mx-imgBorder"]
-      > ![A screenshot of the untrusted extensions window. "Allow" is highlighted in red.](media/untrusted-extensions.png)
-
-
 ## Add an MSIX image to the host pool
 
 Next you'll need to add the MSIX image to your host pool.
@@ -153,9 +144,6 @@ To publish the apps:
 
 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.
 
->[!NOTE]
->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.
-
 ## Change MSIX package state
 
 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.