Microsoft Technology Licensing, LLC

Joel Tipke

Daniel Ward

Jerry Kane Orman

Nicholas Claunch

Ulric Tyson Dihle

Shopen Patel

Chrystal Danielle Comley

Seth Scruggs

Peter Theeuwen

Jacob Orchard

Balakrishnan Shanmugam

Ralph Foster

Geoffrey Naismith DeFilippi

Michael Ernest Bailey

Charles Clayton Gardner

Grant D Goodall

Representative embodiments disclose mechanisms for data and identity migration, such as from an on-premises environment to a cloud environment. The system comprises multiple data collectors, each tailored to collect data from a data source. In a representative example, data collectors for a source application, a source identity repository and a target identity repository are utilized. Once the data is collected, it is stored in a database and methods are used to identify correlations (i.e., matches) between the source application data, the source identity repository data and the target identity repository data. The correlations are memorialized and presented to a user for rationalization. The process is stateful so that prior decisions are remembered. Once the user is satisfied with the rationalization, the system exports files that are consumed by a migration process to perform the actual data migration.

Identity mapping for cloud migrations

Aspects of the present disclosure relate to systems and methods for providing a shared command history. In one aspect, a shared command history is enabled for performing at least one process using a command line interface. One or more commands entered in the command line interface may be sent to a shared storage location. One or more commands stored in the shared storage location and executed using at least another command line interface may be received. The shared command history may be displayed in the command line interface. In one example, the shared command history includes at least the one or more received commands.

Shared command history

Representative embodiments disclose how to remove spilled data from an unauthorized system and/or service in a cloud service. Some embodiments allow a user to remove spilled data in a secure fashion without involving an administrator. Spilled data resides in a data structure backed by allocated storage locations. The system presents a user interface allowing a user to enter information that allows identification of the allocated storage locations. The spilled data is removed from the data structure leaving whitespace in the allocated storage locations where remnants of the spilled data can reside. The system creates a copy of the data structure, removing the whitespace. The system connects the copy of the data structure in place of the original data structure. The original allocated storage locations are then overwritten in a secure manner to remove any remnants of the spilled data.

Secure removal of sensitive data

Growing community of inventors

Seattle, WA, United States of America

Joel Tipke