Merge pull request #896 from MicrosoftDocs/main

Documentation updates

msix-src/app-installer/app-installer-authentication-manager--overview.md

@@ -1,24 +1,23 @@
 ---
 title: App Installer Authentication Manager
 description: Overview of the App Installer Authentication Manager
-ms.date: 4/15/2021
+ms.date: 4/07/2023
 ms.topic: article
 keywords: windows 10, uwp, app installer, AppInstaller
 ---
 
 # App Installer Authentication Manager
 
-The Microsoft Desktop App Installer supports OAuth 2.0 authentication requests for identities hosted in Microsoft Azure Active Directory (AAD), Google, and Dropbox to access the Windows app installation media. The user will only be prompted for authentication if the Windows app installation media is inaccessible, by first attempting to access the media for display to the user. 
+The Microsoft Desktop App Installer on Windows 11, supports OAuth 2.0 authentication requests for identities hosted in Microsoft Azure Active Directory (AAD), Google, and Dropbox to access the Windows app installation media. The user will only be prompted for authentication if the Windows app installation media is inaccessible, by first attempting to access the media for display to the user. 
 
 If authentication is required, the URI targeting the installation media must provide the identity hosting solution by including the suffix of `?msixauth=<identity provider>` to the URI. By specifying the identity provider, the Microsoft Desktop App Installer will connect to the desired identity provider to request authentication.
 
 | Identity Service  | Identity Connection String  |
 |-------------------|-----------------------------|
 | Microsoft AAD     | msixauth=aad                |
-| Google            | msixauth=google             |
-| Dropbox           | msixauth=dropbox            |
 
 > [!Note]
-> The values of each field must be URL-encoded, that is with non-printing characters and spaces. The use of question mark ("?") to seperate the main Source from the field values, and ampersands ("&") to seperate each subsequent fields in the `ms-appinstaller:`.
+> 1.  The values of each field must be URL-encoded, that is with non-printing characters and spaces. The use of question mark ("?") to separate the main Source from the field values, and ampersands ("&") to separate each subsequent fields in the `ms-appinstaller:`.
+>     Example: `ms-appinstaller:?source=https://website.com/app.msix&msixauth=aad`
 > 
-> Example: `ms-appinstaller:?source=https://website.com/app.msix&msixauth=aad`
+> 2. The authentication is only supported for the MSIX itself. The .appinstaller file itself cannot also be hosted on an AAD server.

msix-src/packaging-tool/tool-overview.md

@@ -28,6 +28,11 @@ If you are interested in being an MSIX Packaging Tool insider, click [here](insi
 
 To install the MSIX Packaging Tool from the Microsoft Store, go [here](https://www.microsoft.com/p/msix-packaging-tool/9n5lw3jbcxkf), making sure you are logged in with the MSA that is used for your Windows Insider Program. Next, go to the product description page and click the Install icon to begin the installation.
 
+MSIX Packaging Tool can be installed from WinGet command-line tool using the command -
+```
+PS C:\> winget install "MSIX Packaging Tool"
+```
+
 MSIX Packaging tool can also be downloaded for offline use in the enterprise from Microsoft Store for Business [web portal](https://businessstore.microsoft.com/). You can learn more about offline distribution [here](/microsoft-store/distribute-offline-apps#download-an-offline-licensed-app).
 
 After you have the offline version of the application, you can use [PowerShell](/powershell/module/dism/add-appxprovisionedpackage?view=win10-ps&preserve-view=true) to add the app package and license to your machine.