Updated: August 27, 2013
Applies To: Windows 8, Windows 8.1
The PrivilegedApplications element specifies the app that will be allowed to access privileged Mobile Broadband interfaces.
There are no attributes.
The app that should have access to the privileged Mobile Broadband interfaces.
<xs:element name="PrivilegedApplications" type="tns:PrivilegedApplicationsType" minOccurs="0" /> <xs:complexType name="PrivilegedApplicationsType"> <xs:choice> <xs:element name="AnyApplication" type="tns:AnyApplicationType" /> <xs:element name="Package" type="tns:PackageForPrivilegedApplications" maxOccurs="unbounded" /> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xs:choice> </xs:complexType>
The PrivilegedApplications element allows a specified app to access the Mobile Broadband and SMS APIs with privileged access rights.
The structure for the package identity is identical with the <Identity> element in the application manifest structure. You should copy the elements from the application manifest.
To specify multiple packages, list multiple Package elements in the PrivilegedApplications element.
The Package Name, Publisher, and Application ID must match the information in package.appxmanifest for the Windows Store app. The publisher also must match the publisher certificate that is installed on the PC.
For the Windows Store app that is listed under the DeviceCompanionApplication element to have access to privileged Mobile Broadband interfaces including SMS, that app also must be specified under the PrivilegedApplications element.
When you are submitting your service metadata package to the Windows Dev Center Dashboard, you cannot declare more than 2 privileged apps. One of apps must be the app ID for the Windows Store device app that will be automatically downloaded. The second privileged app is not automatically downloaded, but will access to the privileged Mobile Broadband APIs if the app is installed.
The PrivilegedApplications element is optional.