Merge pull request #5592 from MicrosoftDocs/Ankur/Edit-Elevation-capability-usage-notes

Update app-capability-declarations.md

Author: GrantMeStrength

uwp/packaging/app-capability-declarations.md

@@ -250,7 +250,7 @@ The following table lists the restricted capabilities. You may request approval
 | **Broad Filesystem Access** | The **broadFileSystemAccess** capability allows apps to get the same access to the file system as the user who is currently running the app without any additional file-picker style prompts during runtime. It is important to note that this capability is not required to access files that the user has already chosen using the FilePicker or FolderPicker.<br/><br/>This capability works for the [Windows.Storage](/uwp/api/windows.storage) APIs. Because users can grant or deny the permission any time in Settings, you should ensure that your app is resilient to those changes. In the April 2018 update, the default for the permission is On. In the October 2018 update, the default is Off. It is also important that you do not declare any special folder capabilities such as **Documents**, **Pictures**, or **Videos** with this capability. You can enable this capability in your app by adding **broadFileSystemAccess** to your manifest. For an example, see the [File access permissions](../files/file-access-permissions.md) article.<br/><br/>In most cases, to get access to file system locations, your app can use the [**FileOpenPicker**](/uwp/api/windows.storage.pickers.fileopenpicker), [**FileSavePicker**](/uwp/api/windows.storage.pickers.filesavepicker), [**FolderPicker**](/uwp/api/windows.storage.pickers.folderpicker), and [**FutureAccessList**](/uwp/api/windows.storage.accesscache.storageapplicationpermissions.futureaccesslist) APIs. If you want to request approval to use the *broadFileSystemAccess* capability, then you must provide specific reasons as to why those APIs aren't sufficient for your needs.<br/><br/>**Note:** This capability is not supported on Xbox. |
 | **System Firmware and BIOS** | The **smbios** capability allows apps to access bios data and system firmware data. |
 | **Full Trust Permission Level** | This is the **runFullTrust** restricted capability. Terms are defined below, but in short, a package needs this capability if the package uses features for which full trust is needed. A common example is a package that contains one or more full-trust apps. The **runFullTrust** restricted capability allows a package like that to be installed on a machine.<br/><br/>A *full trust* app is one that sets `uap10:TrustLevel` to *mediumIL* (see the [Application](/uwp/schemas/appxpackage/uapmanifestschema/element-application) element). A full trust app has a process that runs with an integrity level of *medium* (see [Mandatory Integrity Control](/windows/win32/secauthz/mandatory-integrity-control)). And a *package* is an `.appx` or MSIX package (see [Building an MSIX package from your code](/windows/msix/desktop/source-code-overview)).<br/><br/>Another example where this capability is needed is a package with an extension category of *windows.firewallRules* (see [desktop2:Extension](/uwp/schemas/appxpackage/uapmanifestschema/element-desktop2-package-extension)). That's considered a full-trust feature; and in that example there's no app to activate, and no process to launch.<br/><br/>To use the [FullTrustProcessLauncher class](/uwp/api/windows.applicationmodel.fulltrustprocesslauncher), this capability is required, too. |
-| **Elevation** | The **allowElevation** restricted capability allows apps that are created by Microsoft partners and enterprises to preserve existing desktop functionality that requires auto-elevation on launch or during an app's lifetime.<br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved. It will only be approved for line-of-business apps deployed by enterprises to their private store via the Microsoft Store for Business.  |
+| **Elevation** | The **allowElevation** restricted capability enables apps developed by Microsoft partners or enterprise organizations to maintain existing desktop functionality that depends on auto-elevation, either at launch or during runtime.<br/><br/>For Microsoft Store submissions, this capability is subject to approval under strict criteria. If you intend to use this capability, contact [email protected] in advance with a detailed justification. |
 | **Windows Team Device Credentials** | The **teamEditionDeviceCredential** restricted capability allows apps to access APIs that request device account credentials on a Surface Hub device running Windows 10, version 1703 or later.<br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved. |
 | **Windows Team Application View** | The **teamEditionView** restricted capability allows apps to access APIs for hosting an application view on a Surface Hub device running Windows 10, version 1703 or later.<br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved. |
 | **Camera Processing Extension** | The **cameraProcessingExtension** restricted capability allows apps to process images captured from the camera without direct camera control.<br/><br/>This capability is required to call APIs in the [Windows.Devices.PointOfService.Provider](/uwp/api/windows.devices.pointofservice.provider) namespace.<br/><br/>Anyone may request access to this capability for store submission. |