Edit

Device Metadata Business Rules

  • Article

When you submit device metadata packages through the Dashboard, you should ensure that:

  • Packages are downloaded for the correct device.

  • The right package is clearly identified by the associated hardware IDs and model IDs and no conflict exists.

  • Preview packages are not downloaded as released packages.

General rules for submitting device metadata

The following general rules apply when you submit a package through the Dashboard.

  • All packages must be free from malicious software.
  • Each of your device metadata packages must be signed with your company's Microsoft Authenticode certificate.
  • The name of each experience that your company has created must be unique in your company.
  • The friendly name of a package must be unique in the experience that contains the package.
  • The original file name for a package must be unique.
  • All hardware IDs in all packages must be unique. A hardware ID can't match a hardware ID in another experience created by your company or by another company.
  • All model IDs in all packages must be unique. A model ID can't match a model ID in another experience created by your company or by another company.
  • A link to any valid logo submission for a device must be included in the device metadata submission. Each of those valid logo submissions must include the primary device category that is listed in the device metadata submission.
  • To update a package in an existing experience, you must first delete the existing package, create a new package, and then upload the new package to the existing experience.
  • A package can contain no more than 1,000 IDs. This includes hardware IDs and model IDs.

Device metadata types

Different types of device metadata packages must follow different rules. Additionally, different device categories within Device Stage metadata must follow specific rules.

Metadata type Applies to Requirements

Devices and Printers Folder

  • All devices

  • Devices that have a UWP device app

  • Devices that have a privileged app

The device must either use only in-box drivers that do not have an associated Windows® logo submission, or custom drivers that have Windows logo submissions that are bound to the device experience.

Device Stage

  • Digital still cameras

    • Imaging.Camera

  • Portable media players

    Multimedia.PMP

  • Cellular phones

    • Communication.Phone.Cell

  • Printers, fax machines, and scanners

    • PrintFax

    • PrintFax.Fax

    • PrintFax.MFP

    • PrintFax.Printer

    • PrintFax.Printer.Inkjet

    • PrintFax.Printer.Laser

    • PrintFax.Printer.3D

    • Imaging.Scanner

  • Computer

    • Computer.AllInOne

    • Computer.Desktop

    • Computer.Desktop.LowProfile

    • Computer.Desktop.Pizzabox

    • Computer.Laptop

    • Computer.Lunchbox

    • Computer.Netbook

    • Computer.Notebook

    • Computer.Notebook.Sub

    • Computer.Portable

    • Computer.Rackmount

    • Computer.Sealed

    • Computer.Server

    • Computer.SpaceSaving

    • Computer.Tablet

    • Computer.ThinClient

    • Computer.Tower

    • Computer.Tower.Mini

  • Keyboards and mice

    • Input.Keyboard

    • Input.Mouse

    • Input.Trackball

  • Smartcards

    • PersonalIdentity.Smartcard

    • Media.Smartcard

  • Mobile broadband devices

    • Network.MobileBroadband

  • Webcams

    • Imaging.Webcam

  • Generic portables

    • Other.Portable

Each device must have a Windows logo submission.

Experience rules

  • All the device metadata packages in a single experience must support the same hardware IDs and model IDs.

  • In an experience, when you combine a specific locale, preview status, and Windows operating system in a package, the combination must be unique in every package in the experience. For example, in your experience, for Locale A, you can include one released package and preview package for each Windows operating system. That same experience may not include any other release or preview packages for Locale A and for that Windows operating system.

  • In an experience, you can only have one default preview locale package and one default released package for each Windows operating system version.

Unique Device Stage Metadata Submissions

To submit a PC metadata package, see, Submit a PC device manifest package.

To submit a mobile broadband metadata package, see Submit a mobile broadband device manifest package.

To submit a multiple-locale metadata package, see Submit a Multiple-locale device manifest package.

UWP device app limits

Device manufacturers are limited in the number of UWP apps that may be specified in device metadata for automatic installation and app privilege. For example, peripheral device manufacturers (IHVs) can submit up to one app that is configured for automatic installation and up to one app that is specified as a privileged app. An IHV can submit one app that meets both limitations or two apps, with each meeting just one of the limitations.

Important

There is no limit to the total number of UWP device apps that a device manufacturer can submit to the Microsoft Store; these limits apply only to a single device metadata package.

Mobile operators and OEMs have different limits on the number of apps that they can specify in device metadata. For more info, OEMs should contact their Microsoft OEM representative.

In each device metadata package, the following limits apply:

Developer Automatic installation app limit Privileged app limit
IHV 1 1
Mobile operator 1 8
OEM contact Microsoft contact Microsoft