Abstract: Various embodiments of the present technology generally relate to scheduling meetings. More specifically, some embodiments relate to generating customized meeting invites with attendee specific meeting attributes. Some embodiments provide for an invitation tool (e.g., that may be part of a mailbox server) that can automatically identify attendee preferences, create custom polls to gather attendee information, and easily generate custom invitations. In some embodiments, the invitation tool can generate separate individualized links that provides access to a poll with customized attributes based on local environments of each of the plurality of individuals. The tool can analyze the poll responses and then generate custom invites for each attendee by altering one or more attributes or fields. For example, if one attendee is attending remotely, their invite may be altered to only show the remote conferencing information where as other attendees receive invites with only a physical location.

Abstract: Various embodiments of the present technology generally relate to systems and methods for attracting new users to create new e-mail accounts. More specifically, some embodiments provide for systems and methods for generating a new user base by offering attractive e-mail addresses. The attractive or preferred e-mail addresses may be shorter than the current e-mail address being used, have a particular format, belong to a particular domain, or the like. This email address can be reserved for few days and an invitation can be sent. In some embodiments, the invitation can be added at the end of an e-mail sent by another user or automatically generated from the system itself. When a recipient clicks on the link, the mailbox can be activated for use. In some embodiments, the system may offer a migration service to transfer e-mails from the original e-mail address to the new e-mail address.

Abstract: When a meeting time for attendees of a meeting is unavailable, a free/busy listener is configured to detect a change in free/busy data for any of the attendees. When the change is detected, free/busy analysis is performed to see whether a meeting time is available. If so, a control signal is generated to control the calendar systems of the attendees in order to schedule the meeting at the identified meeting time.

Abstract: A calendar sharing invitation is received, and a receiver of the information is identified. The calendar sharing information is sent to the receiver, and the sharer's calendar data is synchronized to a computing system corresponding to the receiver. The sharer's calendar data is synchronized to a pre-accept memory, where it is hidden from the receiver until the receiver provides an input indicating that the receiver accepts the calendar sharing invitation. The sharer's calendar data is then exposed to the receiver for interaction by the receiver.

Abstract: Migrating data from a source data store to a destination data store and validating the migrated data. The method includes migrating data from a first data store to a second data store using a first protocol to create a first set of comparison data. The method further includes migrating the data from the first data store to the second data store using a second protocol to create a second set of comparison data. The method further includes comparing the first set of comparison data to the second set of comparison data. The method further includes validating migration of the data from the first data store to the second data store based on comparing the first set of comparison data and the second set of comparison data.

Abstract: Described is a system and method for automatically updating an attendee list of an electronic meeting invitation. The updated attendee list is sent to the meeting organizer and each invited attendee. The updated attendee list is included in an electronic message that is processed by an electronic communication application but does not appear in an electronic mailbox associated with the electronic communication application.

Abstract: Described is a system and method for automatically updating an action item in an electronic communication application using a single input or click from a user. In response to received input, an electronic communication having a mailto link is automatically generated. The mailto link includes the email address of the intended recipient, an identifier associated with the action item, and the update that is to be performed on the action item. The electronic communication is then automatically provided to the intended recipient and the update is performed on the action item.

Abstract: To improve the responsiveness of a user device during a synchronization of a local calendar with a master calendar, the master calendar will provide the most-relevant events, relative to the current time, first to the user device. The user device is thus enabled to display those most-relevant events to the user.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.

Abstract: Examples of the present disclosure describe systems and methods relating to an automatic meeting invite processor. When processing a meeting invite, the automatic meeting invite processor may enforce a calendar booking rule, which may be comprised by a predicate and an action. The predicate may specify characteristics relating to the meeting invite, such as a sender, scheduled date/time, scheduled location, etc. The predicate may also relate to context associated with a recipient of the meeting invite (e.g., the recipient's calendar or mailbox content). When a predicate is satisfied, the automatic meeting invite processor may perform one or more actions, wherein an action may relate to the meeting specified by the meeting invite or to the meeting invite object itself. Thus, when the predicate is satisfied, the meeting invite may be automatically processed by the automatic meeting invite processor using the action specified by the calendar booking rule.

Abstract: Providing series level updates for a series. A method includes identifying a master message. The master message is a series level message that includes a plurality of default properties for an ordered series. An ordered series of instance messages related to the series level message is identified. For each instance message in the ordered series of instance messages, one or more properties are identified that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message. A default property value from a corresponding property of the master message is propagated to each of the identified properties. The ordered series is propagated to one or more legacy clients that are unable to consume certain series level messages by propagating the ordered series of instance messages with the updated property values.

Abstract: Adding an instance to a series in a fashion that preserves the series for both modern and legacy systems, even when the addition would not ordinarily be compatible with the legacy system. A method includes identifying a master message. The master message includes default values for events in the series. The method further includes identifying user input for a new event in the series. The user input identifies exceptions to the default values. The method further includes creating an instance message that includes default values from the master message for which there are no exceptions identified in the user input and includes the exceptions from the user input.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to receive a record generation request that includes a set of attributes and to generate a record in a computing system based on the record generation request, wherein the record includes the set of attributes and an owner property that identifies a first user as an owner of the record. The architecture comprises a record security component configured to receive a record modification request that requests a modification to the record, to analyze an identifier in the record modification request that identifies a second user as a sender of the record modification request, and to process the record modification request based on an analysis of the identifier in the record modification request relative to the owner property of the record.

Abstract: Adding an instance to a series in a fashion that preserves the series for both modern and legacy systems, even when the addition would not ordinarily be compatible with the legacy system. A method includes identifying a master message. The master message includes default values for events in the series. The method further includes identifying user input for a new event in the series. The user input identifies exceptions to the default values. The method further includes creating an instance message that includes default values from the master message for which there are no exceptions identified in the user input and includes the exceptions from the user input.

Abstract: The techniques described herein facilitate sharing electronic cloud-based calendars via online application and collaboration services, e.g., Microsoft Office 365®. In an implementation, a method of operating an online application and collaboration service for sharing electronic calendars between mailboxes is disclosed. The method includes receiving a request to share a master calendar owned by a first user of the online application and collaboration service with a second user. The master calendar is stored in the first user's mailbox. The method further includes communicating a response indicating acceptance of the request to share the master calendar, generating a copy of the master calendar in the second user's mailbox, and synching the copy of the master calendar with the master calendar using pre-cached data to populate an initial view.

Abstract: Availability data caching in, meeting services is provided. In some examples, a list of users whose data is to be cached locally for a user may be determined based on factors such as their relevance to the user, a likelihood of a meeting being requested with the users, a history of common meetings, and similar factors. What type of user data to cache, for how long, at which granularity level, and similar parameters may be determined as well. User data for users from the list may be retrieved on-demand or on a regular basis from server associated with those users and stored at a server or other computing device for the user for fast access when the user requests to schedule a meeting.

Abstract: A method includes identifying a series of events formatted for a modern system. The series of events includes a master message usable by modern systems. The master message includes default information for all events in the series. The method further includes identifying a plurality of instance messages. Each of the instance messages includes default information and exception information for a given event in the series of events. The method further includes sending both the master message and the instance messages to other systems without regard to whether the other systems are modern or legacy systems.

Abstract: Ordering a series of messages when there is a possibility that the messages will be received out of order. A method includes receiving a plurality of messages in a series of messages. Each of the messages in the plurality of messages is stored in a temporary storage container; in anticipation of receiving a master message. A master message is received. The master message defines an ordering for the plurality of messages. The messages in the series of message from the temporary storage to a destination container accessible by a user according to the ordering defined in the master message.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.

Abstract: In an example, a system and method are described for providing trusted updaters and trusted processes. An updater may be subject to a whitelist of files that it, and any child processes, are allowed to modify. But trust inheritance may break across reboots and over interprocess communication. Thus, it is desirable to provide a system and method to maintain trust across such events. In the case of a trusted installer, inheritance may be maintained by cross referencing a digital certificate to a workflow grid. In the case of updater processes, trust may be maintained by using a combination of digital certificates that are part of a trust chain and a unique identifier for each trust chain workflow.