Microsoft Technology Licensing, LLC

Yanan Zhang

Brian Stuart Perlman

Hung Minh Dang

Adrian Francisco Teran Guajardo

Jonathan M Andes

Colin William Hassett

Anni Dong

Hari R Pulapaka

Benjamin M Schultz

Frederick Justus Smith

Balaji Balasubramanyan

Giridhar Viswanathan

Margarit Simeonov Chenchev

Manoj Jain

David Guy Weston

Michael Sean Kirby

Helen Harmetz

Abigail Christine Motley

Padmanabhan Vasu

William Saunders Jack, Iii

Brian Stuard Perlman

This document relates to securing ownership of devices to particular users when the devices are shipped directly from an original equipment manufacturer in order to prevent malicious use of devices that are lost or stolen. A purchaser may purchase a device from an original equipment manufacturer, and as part of the purchasing process, may provide ownership information for the device, which may include a user identifier and an identity provider. The ownership data can be written to firmware, and upon powering on of the device, the device can request a user identifier, which is then validated by the identity provider before allowing operating systems operations to continue on the device.

Secure user assigned device from manufacturer

Techniques are described herein that are capable of registering a user device with a cloud-based management service using an intermediate cloud storage. For instance, the intermediate cloud storage may store an encrypted data blob including information that identifies the user device. The intermediate cloud storage or a registration system may decrypt the encrypted data blob so that the registration system may use the decrypted data blob to register the user device with the cloud-based management service. For instance, the registration system may retrieve the encrypted or decrypted data blob from the intermediate cloud storage by providing a requisite secret to the intermediate cloud storage. The requisite secret may be provided to the registration system by the user device (e.g., via a matrix barcode, such as a QR code).

Cloud-based management service device registration using intermediate cloud storage

This document relates to a process for deploying devices and automatically provisioning the devices to connect to a managed network upon powering on with minimal user involvement. Upon deployment of the device to an end point, a record can be established in a management server regarding the device, which can associate device specifications with a deployment profile to be used in provisioning the device. Upon powering on of the device at the end point, the device can automatically perform attestation with the management server, which can then provision the device according to the deployment profile without additional user intervention.

Securely configuring target devices using device identity

Technologies are described for selective persistence of data utilized by software containers. A configuration policy is defined that includes data that specifies one or more data stores for which data is not to be persisted following accesses to a software container and one or more data stores for which data is to be persisted following accesses to the software container. When the software container is first accessed, the data stores identified in the configuration policy are attached to the software container. Upon a subsequent access to the container, such as at the conclusion of a user session or upon destruction of the container, the data in the attached data stores is persisted or deleted based upon the configuration policy. When the software container is once again accessed, the data store containing the persisted data can be re-attached to the software container.

Selective persistence of data utilized by software containers

Growing community of inventors

Bellevue, WA, United States of America

Yanan Zhang