aggregated data from other users in your organization. How it's calculated The statistics are on meetings in your calendar that you've accepted, and where your status is set to Busy. The following meetings are not included: Meetings with no participants than yourself, for example when you block time in your calendar or set reminders. All-day meetings. Meetings marked as Private. Meetings with more than 500 attendees. Email Hours What you see An estimate of how much time you spent sending and reading emails. See how these compare to the company average and to your personal goals. Where the data comes from Your data is collected from your Office 365 mailbox. Company averages are based on aggregated data from other users in your organization. How it's calculated The main rules are: For each email you write (send), we assign 5 minutes. For each email you read (open), we assign 2.5 minutes. However, there are exceptions: If you send one email and then open or send another one within 5 minutes, we assign the time between the two actions to the first email. If you open an email and then open or send another one within 2.5 minutes, we assign the time difference between the two actions to the first email. We register email across all devices, such as laptop or mobile phone. We only include emails where your name, or a group you’re a member of, is on the To or Cc lines. We don’t emails you delete without opening. Email that you read or write outside the work hours are included in After hours. Focus Hours What you see Focus hours are defined as at least two consecutive hours of time without meetings. Where the data comes from Your data is collected from your Office 365 calendar. How we calculate the numbers Sums up the total number of hours in your calendar where you have at least two hours without meetings. Only includes focus hours within your defined work hours. Sending or receiving emails during focus hours doesn’t interfere with the focus hour calculation. After Hours What you see time spent on email and in meetings outside defined work hours, for example emails read or sent on weekends. Where the data comes from Your data is collected from your Office 365 calendar and mailbox. Company averages are based on aggregated data from other users in your organization. How we calculate the numbers See Meetings and Email hours
Scenarios Simplifies the eDiscovery process across your email and document repositories This new machine learning & analytics functionality improves existing eDiscovery by: Significantly reducing document review Speeding up the document review process. core technology (Equivio) that has already achieved broad acceptance in the legal community. Resources Watch Videos … Read … MSIT Showcase: MFA for Office 365 (MFA) MFA helps secure user sign-ins for cloud services beyond just a single password. The security of multi-factor authentication lies in its layered approach. Compromising multiple authentication factors presents a significant challenge for attackers. Even if an attacker manages to learn the user's password, it is useless without also having possession of the trusted device. Should the user lose the device, the person who finds it won't be able to use it unless he or she also knows the user's password. Office 365 uses authentication to help provide the extra security and is managed from the Office 365 admin center. Features Office 365 offers the following subset of Azure multi-factor authentication capabilities as a part of the subscription: The ability to enable and enforce multi-factor authentication for end users The use of a mobile app (online and one-time password) as a second authentication factor The use of a phone call as a second authentication factor The use of a Short Message Service (SMS) message as a second authentication factor Application passwords for non-browser clients Default Microsoft greetings during authentication calls Feature comparison of versions A form of multi-factor authentication is included with Office 365, but you can also purchase Azure Multi-Factor authentication that includes extended functionality. The following below provides a list of the features that are available in the various versions of Azure Multi-Factor Authentication. Feature O365 MFA Azure MFA Administrators can protect accounts with MFA ● ● Mobile app as a second factor ● ● Phone call as a second factor ● ● SMS as a second factor ● ● App passwords for clients that don't support MFA ● ● Admin control over authentication methods ● PIN mode ● Fraud alert ● MFA Reports ● One-Time Bypass ● Custom greetings for phone calls ● Customization of caller ID for phone calls ● Event Confirmation ● Trusted IPs ● Suspend MFA for remembered devices (Public Preview) ● MFA SDK ● MFA for on-premises apps using MFA server ● Resources
365 & Office 365 includes many security and information protection capabilities. Microsoft Enterprise Mobility + Security (EMS) includes additional capabilities for protecting data, identities, and devices with Office 365. EMS includes Microsoft Intune and Azure Active Directory Premium. It can be challenging for large organizations to determine which capabilities to implement and in what order. The article provides help. Deciding which capabilities to use Our cybersecurity consulting team recommends taking a methodical approach to planning and implementing security and information protection features. If you don’t already have an established approach, here is a recommended starting point. Step 1: Set information protection standards First, agree on a set of standards that can be applied across your organization. Here is an example of what this can look like. A Establish information protection priorities The first step of protecting information is identifying what to protect. Develop clear, simple, and guidelines to identify, protect, and monitor the most important data assets anywhere they reside. B Set organization minimum standards Establish minimum standards for devices and accounts accessing any data assets belonging to the organization. This can include device configuration compliance, device wipe, enterprise data protection capabilities, user authentication strength, and user identity. C Find and protect sensitive data Identify and classify sensitive assets. Define the technologies and processes to automatically apply security controls. D Protect high value assets (HVAs) Establish the strongest protection for assets that have a disproportionate impact on the organizations mission or profitability. Perform stringent analysis of HVA lifecycle and security dependencies, establish appropriate security controls and conditions. Step 2: Classify data by sensitivity level Three levels is a good starting point if your organization doesn’t already have defined standards. Step 3: Map service capabilities to data sensitivity levels Some information protection capabilities broadly and can be used to set a higher minimum standard for protecting all data. Other capabilities can be targeted to specific data sets for protecting sensitive data and HVAs. This table includes an example of how capabilities can be mapped to data sensitivity levels. There are two examples for level 1 because the default service will meet this need for some organizations while others require greater protection. Level Standard Description 1 Data is encrypted and available only to authenticated users This of protection is provided by default for data stored in Office 365 services. Data is encrypted while it resides in the service and in transit between the
Self service operations for the end users, like site collection provisioning for cloud or for on-premises with service bus usage Route entries or information from Office 365 to systems Resources Watch Videos Read Office 365 Developer Patterns and Practices The Office 365 Developer Patterns and Practices program provides samples and documentation to help you transition your development solutions from full-trust code to the app model. Start by reading . You can use the code samples and guidance in the project to help you develop business solutions for your organization or your customers. The project includes code samples that show you how to use provider-hosted add-ins to address key scenarios, as well as other resources that illustrate best practices for add-in model development. Must Read: The on MSDN provides samples and documentation to help you to implement typical customizations for Office 365 or for SharePoint Online on your functional requirements. The GitHub repo - houses all of the training content for Office 365 Development training courses. Videos related to the guidance are available on the on Channel 9. PnP weekly web casts are quick videos recorded around key topics for the Office 365 and SharePoint add-in model development. These are around 30-45 min long recordings on different resources, guidance and other patterns and practices. All web casts will be published to . Office 365 Dev PnP releases are done typically Friday of each month. Details on monthly releases are covered in the monthly community calls. to save the call details to your calendar. Resources . One location for all the latest resources and announcements . Main repository