Microsoft Technology Licensing, LLC

Venkata Raghuram Pampana

Peter J Kaufman

Shayak Lahiri

Brian Stuart Perlman

Sean Anderson Bowles

Haipeng Li

Manoj Jain

Peter John Richards

Dhruma Kishan Parikh

Yordan Ivanov Rouskov

Marc Shepard

Gaurav Raghu Dhawan

Prabagar Ramadasse

Ramachandra Ravitej Vennapusa

Mick Healy

Aleksandr Tokarev

Loretta Marie Macklem-Clements

Annie Guo Joli-Coeur

Generally discussed herein are devices, systems, and methods for binding with cryptographic key attestation. A method can include generating, by hardware of a device, a device public key and a device private key, based on the device private key, signing a first attestation resulting in a signed first attestation, the first attestation claiming the device private key originated from the hardware, based on the device public key and the signed first attestation, registering the device with a trusted authority, generating, by the hardware, a first application private key and a first application public key, and based on the device private key, signing a second attestation resulting in a signed second attestation, the second attestation claiming the first application private key originated from the hardware, and based on the first application public key and the signed second attestation, registering a first application of the device to a first server.

Binding with cryptographic key attestation

This document relates to a process for supporting the management of a variety of types of deployed devices. Administrators utilizing enterprise services can provide generic configuration data using configuration templates, which can be provided to a management server. The management server can then precompute device-specific configuration settings and resolve any conflicts that may arise based on the configuration templates. The configuration templates can also include placeholders for secret values, and once a managed device checks in to the management server, the secret values can be retrieved from an applicable enterprise service and provided to the managed device at the time of applying the configuration template.

Secure management of devices

This document relates to a process for managing remote devices within an organization. Upon receiving device state information from the remote device, a cloud-based management server can analyze the device state information of the remote devices, and categorize the remote devices into a number of categories that reflect each device's state with respect to co-management enrollment. The categories can be presented to a user in order to provide a comprehensive view of the state of various remote devices in relation to their co-management state. Various co-management enrollment actions can then be issued to the remote devices in order to enroll a device in co-management, or upgrade a co-management category associated with the device.

Co-management eligibility and enrollment

Growing community of inventors

Redmond, WA, United States of America

Venkata Raghuram Pampana