Lync Online: PowerPoint Sharing Feature

Using Lync and PowerPoint, an Office 365 user can give PowerPoint presentations, record them, and work collaboratively on PowerPoint slides during a Lync Meeting with as many as 249 other people. This article describes how to use this feature.   Author : Alexandra Lise Publication date : November 6, 2012 Product version : Lync Online   Lync’s sharing feature gives Office 365 users a way to share PowerPoint presentations with colleagues in different locations. Users can present information from slides or take advantage of Lync’s collaboration features and work together on a presentation to be delivered later. Collaboration features enable users to give control to other users while the annotation tools help groups focus on certain parts of a presentation. Sharing sessions can be done ad hoc or during a scheduled Lync Meeting. Getting Started To help Lync Online users set up a sharing session , point them to the following topics:   Set up a Lync Meeting — explains how to schedule an online meeting by using Outlook or Lync Web Scheduler . TIP: To be able to set up Lync Meetings users must be enabled for dial-in conferencing. For details, see Configure Dial-in Conferencing .   Start an impromptu Lync Meeting — explains how to invite one person or a group of people to join a Lync IM conversation and add audio and/or video. Presenting and Recording To give a presentation 1. In a meeting or conversation window, pause on the presentation (monitor) icon, and then click PowerPoint . Figure 1. Selecting PowerPoint in the meeting window. 2. Options: To move the slides, use either the arrows at the bottom of the meeting window or click Thumbnails , and then click the slide you want to show To see your presenter notes, click Notes . To use the laser pointer, highlights, shapes, the eraser, pen, text changer, and other annotation tools, on the upper-right side of the slide, click the Annotations button — then click the type of annotation you want to use. Note : annotating doesn’t change the actual file, although, if you want to, you can save an annotated copy. To prevent someone from skipping ahead or using annotations, in the meeting window, click More Options , click Lync Meeting Options , and then select the permissions level for the participant(s). To record a presentation 1. In the meeting or conversation window, click More Options , and then click Start Recording Figure 2. Figure 2. Starting recording. 2. (Optional) Use the controls at the bottom of the window to pause and resume recording. 3. When finished, click the Stop Recording button. Lync automatically saves the recording in a format that plays in Windows Media Player and Zune. Figure 3. Stopped recording notification. To manage a presentation To prevent people from downloading the presentation, during a sharing session, hover over presentation (monitor) icon, click the Manage Presentable Content button, and then click the Permissions menu and the appropriate option. To prevent people from annotating or skipping ahead, in the meeting window, click Meeting Options , click Lync Meeting options , and then select the appropriate permissions. To save someone else’s presentation or an annotated copy, during a sharing session, pause on the presentation (monitor) icon, click the Manage Presentable Content button, click More , and then select the saving option. To edit a presentation together To give control to another person, click Give Control on the sharing bar at the top of your meeting window. Then either click an individual attendee or click Give Control Automatically to grant control to anyone who requests it during the sharing session. To take back control at any time click the Give Control again, then click either the name of the person who has control or Give Control Automatically if it’s selected. Lync’s sharing and collaboration tools, combined with PowerPoint’s ability to organize and feature important information, give Office 365 users an effective way to present information to remote users in large and small audiences, It also enables users to work with colleagues— in scheduled or impromptu sessions— to develop, refine and style presentation content. Additional Resources To learn more, check out the following articles: Lync 2013 for Office 365 Sharing and Collaboration Quick Reference Record and Playback a Lync Meeting Introduction to the Lync Meeting Window   Keywords : Lync Meeting, PowerPoint, present, annotations

Connecting a Project Task Pane App to PWA

Introduction Apps for Office present a great new opportunity to bring data from a variety of sources into Office applications. The new Project specifically offers a very powerful way to surface both SharePoint and Project Web App data in a task pane app in Project Professional. To connect with SharePoint or PWA from the client, we use on-the-fly OAuth flow as presented in the SharePoint 2013 SDK . The App for Project described in this article connects with the same PWA site collection that Project Professional is currently connected to, and displays data about the currently selected task that is not otherwise available from within Project Professional. This will work with all versions of Project Professional (C2R, MSI, On Demand) and with all PWA environments (Project Online, Project Server). Setup Prerequisites for this project are: Visual Studio 2012 IIS or IIS Express configured to allow applications to run on your server (at localhost) Office 2013 and SharePoint 2013 tools for Visual Studio, available here Project Professional 2013 Project Online tenant or Project Server The first step is to launch Visual Studio 2012. Create a new App for Office 2013 project as shown below. Let’s call it “TaskLastModifiedApp”. In the next dialog, make this a Task Pane App for Project. We need to add references, as this app will use a number of APIs across Office and SharePoint. These DLLs may be in a different location on your system. Most of these references are automatically added if you use the App for SharePoint template, so if you can’t find these on your system, create a quick App for SharePoint solution and note the reference paths to help you out. You should add: C:Program FilesReference AssembliesMicrosoftWindows Identity Foundationv3.5Microsoft.IdentityModel.dll C:WindowsMicrosoft.NETassemblyGAC_MSILMicrosoft.IdentityModel.Extensionsv4.0_2.0.0.0__69c3241e6f0468caMicrosoft.IdentityModel.Extensions.dll C:Program FilesReference AssembliesMicrosoftWindows Identity Foundationv3.5Microsoft.IdentityModel.WindowsTokenService.dll C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15ISAPIMicrosoft.ProjectServer.Client.dll C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15ISAPIMicrosoft.SharePoint.Client.dll C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15ISAPIMicrosoft.SharePoint.Client.Runtime.dll C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.0System.IdentityModel.dll C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.0System.IdentityModel.Selectors.dll C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.0System.ServiceModel.dll Additionally, you will need to add a copy of TokenHelper.cs, which is generated when creating an autohosted or provider-hosted App for SharePoint project. Task Pane App Manifest The actual task pane app is just an XML manifest. Open up TaskLastModifiedApp.xml from the TaskLastModifiedApp project in your Solution Explorer. Replace its contents with the following: 1: 2: 3: [leave this line alone] 4: 1.0 5: Microsoft 6: en-US 7: 8: 9: 10: https: //localhost:44301/ 11: 12: 13: 14: 15: 16: 17: 18: ReadWriteDocument 19: Replace the port after localhost (in both instances) with whatever port you have configured IIS to use for SSL. Make sure to toggle the “SSL Enabled” property on the TaskLastModifiedAppWeb project to true. Let whatever ID was originally set in the manifest remain. Architecture Next, delete the TaskLastModifiedApp.html page – we will need .aspx pages in this project. The basic architecture of the task pane app is as follows: When the task pane app is launched, it loads “URLConstructor.aspx”, which pulls the PWA URL from the client and constructs a call to OAuthAuthorize with the proper tokens to request permissions for the app to access PWA data. This page loads “URLConstructor.js” to interact with the client. OAuthAuthorize is launched in a new window, since we cannot predict the customer’s Project domain. After the user trusts the app, that new window is redirected to “PostOAuth.aspx”, which surfaces the auth code back to URLConstructor.aspx. Once URLConstructor.aspx has the auth code, the task pane app is redirected with this as a token to “Default.aspx”, which has the functional code for the app. This page uses Project CSOM code in its code-behind page to read data from PWA, as well as “TaskLastModifiedApp.js” to interact with the client. Constructing the OAuthAuthorize URL The complete code for URLConstructor.aspx is as follows: 1: 2:   3: 4:   5: 6:   7: 8: TaskLastModifiedApp 9: 10: 11: 12: 13: 14: function getClientId() { 15: var clientId = ‘ ‘ ; //read the clientID from web.config 16: getPwaUrl(clientId); //return to client code 17: } 18: 19:   20: 21: Redirecting… 22: 23:   24: This page needs to be an .aspx page in order to read from web.config, but does not need anything in its code-behind. The clientId read from web.config is needed for the authorization flow. getPwaUrl() is a function within URLConstructor.js. The complete code for URLConstructor.js is as follows: 1: var _projDoc; 2: var pwaUrl; 3: var oAuthUrl; 4:   5: Office.initialize = function (reason) { 6: _projDoc = Office.context.document; 7: getClientId(); //on document load, reads the ClientId from web.config first since it is server-side 8: } 9:   10: function getPwaUrl(clientId) { //uses Office App API to read PWA URL 11: _projDoc.getProjectFieldAsync(Office.ProjectProjectFields.ProjectServerUrl, 12: function (asyncResult) { 13: if (asyncResult.status == Office.AsyncResultStatus.Succeeded) { 14: pwaUrl = asyncResult. value .fieldValue; 15: generateUrl(clientId); //creates the OAuthAuthorize URL with necessary parameters 16: } 17: else { 18: logMethodError( “getProjectFieldAsync” ,, asyncResult.error.message); 19: } 20: } 21: ) 22: }; 23:   24: function generateUrl(clientId) { 25: oAuthUrl = pwaUrl + “/_layouts/15/OAuthAuthorize.aspx?IsDlg=1&client_id=” + clientId + “&scope=Projects.Read&response_type=code&redirect_uri=https://localhost:44301/pages/PostOAuth.aspx” ; 26: authWindow =; 27: codeListener(); //start listening for the auth code 28: } 29:   30: function codeListener() { 31: setTimeout(function () { readCode(); }, 1000); //check for the auth code every one second 32: } 33:   34: function readCode() { 35: try { //if we can actually reach the authCode field on PostOAuth.aspx 36: authCode = authWindow.document.getElementById( “authCode” ). value ; //pull the authCode value 37: if (authCode != “NA” ) { //if it is not the default “NA” 38: authWindow.close(); //close the new window 39: document.location.href = “/Pages/Default.aspx?code=” + authCode; //redirect task pane to the app code with the authCode token 40: } 41: } 42: catch (e) { 43: codeListener(); //if we couldn’t reach PostOAuth.aspx, wait another second and try again 44: } 45: } When the task pane app loads, it first reads web.config from the aspx page, since this is server-side code. Once it has the clientId, we read the PWA URL. We then create the full OAuthAuthorize URL with the parameters specified above. scope=Projects.Read requests read permission to projects on the current PWA site. Make sure to match the SSL port here as well, as before. On running the app, a new window will open up outside of Project that prompts the user to login to PWA (if they have not checked “Keep me signed in” previously). They will then be presented with a “Do you trust…” page, the same as if they were installing an App for SharePoint. This is the OAuthAuthorize.aspx page. Once trusted, that new window navigates to PostOAuth.aspx, presented below: 1: 2:   3: 4:   5: 6: 7: 8: 9: 10: 11: 12: 13: Closing… 14: 15: 16: 17: And PostOAuth.aspx.cs: 1: using System; 2: using System.Collections.Generic; 3: using System.Linq; 4: using System.Web; 5: using System.Web.UI; 6: using System.Web.UI.WebControls; 7:   8: namespace TaskLastModifiedAppWeb.Pages 9: { 10: public partial class PostOAuth : System.Web.UI.Page 11: { 12: protected void Page_Load( ob
ject sender, EventArgs e) 13: { 14: var code = Request.QueryString[ “code” ]; 15: authCode.Value = code; 16: } 17: } 18: } This page saves the auth code token in a hidden field. The task pane app, still on URLConstructor.aspx, waits for this value and then closes the new window. The app then continues on to default.aspx with the proper code token needed to finish the OAuth flow. Reading the Last Modified Date of the Selected Task The remainder of this article is an example of what you might do in your task pane app now that you have read access to PWA data. This example will show you the Last Modified date and time of the task you have selected. On launch, it shows you data for the selected task, and as you change tasks, the data is updated using an event handler. The complete code for Default.aspx is as follows: 1: 2:   3: 4:   5: 6: 7: TaskLastModifiedApp 8: 9: 10: 11: 12: 13: 14:   15: 16: 17: 18: 19: 20: 21:   22: 23:   24: 25: 26: 27:   28: 29:   30: 31: This page contains three hidden fields used to pass data back and forth between the client-side code and the server-side code. It also leverages a label to surface the results to the user, and a hidden button that the client-side code uses to call a server-side function, as you will see below. The complete code for TaskLastModifiedApp.js is as follows: 1: var _projDoc; 2: var taskGuid; 3: var projGuid; 4: var pwaUrl; 5:   6: // This runs after every postback 7: Office.initialize = function (reason) { 8: _projDoc = Office.context.document; 9: if (document.getElementById( “pwaUrlHF” ). value == “NA” ) { //if this is the first run 10: firstRun(); 11: } 12: manageTaskEventHandler( ‘addHandlerAsync’ ); //need to re-register event handler after each postback 13: } 14:   15: // Only need these on the first page load, not on postbacks 16: function firstRun() { 17: getProjGuid(); 18: _projDoc.getProjectFieldAsync(Office.ProjectProjectFields.ProjectServerUrl, 19: function (asyncResult) { 20: pwaUrl = asyncResult. value .fieldValue; 21: document.getElementById( “pwaUrlHF” ). value = pwaUrl; 22: } 23: ) 24: getTaskGuid(); 25: } 26:   27: // Get the GUID of the selected task, comes from SDK 28: function getTaskGuid() { 29: var TaskLastModLabel = document.getElementById( “TaskLastModLabel” ); 30: TaskLastModLabel.innerHTML = “Loading…” ; 31: _projDoc.getSelectedTaskAsync(function (asyncResult) { 32: taskGuid = asyncResult. value ; 33: document.getElementById( “taskGuidHF” ). value = taskGuid; //saves the task GUID to a hidden field to pass to the code-behind 34: document.getElementById( “hiddenTaskChangedButton” ).click(); //runs the CSOM calls in the aspx.cs file 35: }); 36: } 37:   38: // Get the GUID of the current project. 39: function getProjGuid() { 40: _projDoc.getProjectFieldAsync(Office.ProjectProjectFields.GUID, 41: function (asyncResult) { 42: projGuid = asyncResult. value .fieldValue; 43: document.getElementById( “projGuidHF” ). value = projGuid; //saves the project GUID to a hidden field to pass to the code-behind 44: } 45: ) 46: } 47:   48: // Task selection changed event handler. 49: function onTaskSelectionChanged(eventArgs) { 50: getTaskGuid(); 51: } 52:   53: // Add or remove a task selection changed event handler. 54: function manageTaskEventHandler(docMethod) { 55: manageEventHandlerAsync( 56: Office.EventType.TaskSelectionChanged, // The task selection changed event. 57: onTaskSelectionChanged, // The event handler. 58: docMethod // The Office.Document method to add or remove an event handler. 59: ); 60: } 61:   62: // Add or remove the specified event handler. 63: function manageEventHandlerAsync(eventType, handler, operation, onComplete) { 64: _projDoc[operation] //The operation is addHandlerAsync or removeHandlerAsync. 65: ( 66: eventType, 67: handler, 68: function (asyncResult) { 69: // code here runs after event has been registered (or failed) 70: } 71: ); 72: } The first time this code runs, it pulls the PWA URL (just like we did in URLConstructor.js) and saves it to one of our hidden fields, registers a client-side event handler to capture when a new task is selected, and starts the process of connecting to PWA and pulling the data we need, which is mostly done in the code-behind file. After each postback, we do not need to recapture the PWA URL, as our ProjectContext is maintained as a static variable. We need to make one quick tweak to TokenHelper.cs first – change GetRealmFromTargetUrl from a private method to a public method. The complete code for Default.aspx.cs is as follows: 1: using System; 2: using System.Collections.Generic; 3: using System.Linq; 4: using System.Web; 5: using System.Web.UI; 6: using System.Web.UI.WebControls; 7: using Microsoft.ProjectServer.Client; 8: using Microsoft.SharePoint.Client; 9:   10: namespace TaskLastModifiedAppWeb.Pages 11: { 12: public partial class Default : System.Web.UI.Page 13: { 14: public static ProjectContext projContext; 15: public static PublishedProject thisProj; 16: public Guid projGuid; 17:   18: protected void Page_Load( object sender, EventArgs e) 19: { 20: if (!IsPostBack) //set values of hidden fields if this is the first page load 21: { 22: projGuidHF.Value = “NA” ; 23: taskGuidHF.Value = “NA” ; 24: pwaUrlHF.Value = “NA” ; 25: } 26: } 27:   28:   29: protected void GetContexts() 30: { 31: var code = Request.QueryString[ “code” ]; //pulls the code token from the request 32:   33: string targetPwa = pwaUrlHF.Value; //pulls the PWA URL from where the Office app API stored it 34:   35: Uri targetPwaUri = new Uri(targetPwa); 36:   37: var tRealm = TokenHelper.GetRealmFromTargetUrl(targetPwaUri); 38:   39: Uri rUri = new Uri( “https://localhost:44301/pages/PostOAuth.aspx” ); //hardcoded link to redirect_uri 40:   41: var clientContext = TokenHelper.GetClientContextWithAuthorizationCode(targetPwa, “00000003-0000-0ff1-ce00-000000000000” , code, tRealm, rUri); 42:   43: projContext = GetProjectContextWithAuthorizationCode(targetPwa, “00000003-0000-0ff1-ce00-000000000000” , code, tRealm, rUri); 44:   45: projGuid = new Guid( “{” + projGuidHF.Value + “}” ); //loads the current project through CSOM 46:   47: var projects = projContext.LoadQuery(projContext.Projects.Where(proj => proj.Id == projGuid)); 48: projContext.ExecuteQuery(); 49: thisProj = projects.First(); 50: } 51:   52: protected void OnTaskChanged( object sender, EventArgs e) //determine the selected task’s last modified date 53: { 54: if (thisProj == null ) 55: { 56: GetContexts(); 57: } 58: 59: var taskGuid = new Guid(taskGuidHF.Value); 60:   61: var tasks = projContext.LoadQuery(thisProj.Tasks.Where(task => task.Id == taskGuid)); //load the selected task off of the project 62: projContext.ExecuteQuery(); 63: PublishedTask thisTask = tasks.First(); 64: string dateMod = thisTask.Modified.ToString( “D” ); //pull out the Modified field on the task 65: string timeMod = thisTask.Modified.ToString( “t” ); 66: TaskLastModLabel.Text = “The selected task was last modified on ” + dateMod + ” at ” + timeMod + “.” ; 67: } 68:   69: public static ProjectContext GetProjectContextWithAuthorizationCode( string targetUrl, string targetPrincipalName, string authorizationCode, string targetRealm,Uri redirectUri) 70: { 71: Uri targetUri = new Uri(targetUrl); 72:   73: string accessToken = 74: TokenHelper.GetAccessToken(authorizationCode, targetPrincipalName, targetUri.Authority, targetRealm, redirectUri).AccessToken; 75:   76: return GetProjectContextWithAccessToken(targetUrl, accessToken); 77: } 78:   79: public static ProjectContext GetProjectContextWithAccessToken( string targetUrl, string accessToken) 80: { 81: Uri targetUri = new Uri(targetUrl); 82:   83: ProjectContext projContext = new ProjectContext(targetUrl); 84:   85: projContext.AuthenticationMode = ClientAuthenticationMode.Anonymous; 86: projContext.FormDigestHandlingEnabled = false ; 87: projContext.ExecutingWebRequest += 88: delegate ( object oSender, WebRequestEventArgs webRequestEventArgs) 89: { 90: webRequestEventArgs.WebRequestExecutor.RequestHeaders[ “Authorization” ] = 91: “Bearer ” + accessToken; 92: }; 93:   94: return projContext; 95: } 96: } 97: } PageLoad() The f
irst time the page loads, we need to initialize the hidden field values. This enables us to not set them directly in Default.aspx (and thus lose their values after a postback) and lets the client-side code distinguish between a first run load and a postback. GetContexts() This code also only runs once, assuming the current project remains loaded. This handles the last part of the OAuth flow – we use the code token from OAuthAuthorize to generate a client context and a project context using methods in TokenHelper.cs, as well as slightly modified methods GetProjectContextWithAuthorizationCode() and GetProjectContextWithAccessToken(). OnTaskChanged() This first checks to make sure we have a project loaded from which to pull data. We then read the selected task guid from the hidden field, which was updated client-side before this method was called. We use Project CSOM to load the selected task from PWA and read its Last Modified field, which is then presented to the user in a readable format using the label on Default.aspx. Register the App ID and App Secret Since we are not submitting this app to the Office Store, we need to register it on our test tenant. On your tenant, navigate to https://[your PWA site]/_layouts/15/appregnew.aspx. Generate a new App Id and App Secret, set the Title to “TaskLastModifiedApp”, set the App Domain to localhost:44301 (or wherever the app code is running), and set the Redirect URI to match the redirect_uri token value in the oAuth URL created in URLConstructor.js. Hit Create, and then add the App Id and App Secret to web.config in your Visual Studio solution. It should look like the following when you are done, with your values for ClientId and ClientSecret: 1: 2:   3: 4: 5: 6: 7: 8: 9: 10: 11: Time to Test! To run the app, just hit F5 in Visual Studio, which will launch Project Professional. Make sure to connect to a PWA profile, then load a published project (or create and publish a new one). From a task view, select the Project tab in the ribbon, hit the dropdown for Apps for Office, and click TaskLastModifiedApp. The app will launch in a task pane on the right side of the screen. It’ll prompt you to trust the app, quickly load, and then display the last modified date and time of the selected task. Select a different task, and the data will update almost instantly. Wrap-Up In this blog post, you have learned how to create a task pane app in Project Professional that can display data from PWA that would not normally be visible in the client. The app uses SharePoint’s OAuthAuthorize page to request permissions from PWA and handle the authentication handshake between the app code and your online data. For more on working with OAuth, make sure to check out the relevant node in the SharePoint 2013 SDK. For more information on PWA programmability, check out the Project 2013 SDK . To learn more about writing task pane apps for the new Project, see this node in the Office 2013 SDK .

New Office Web Apps Features Coming Your Way

One of the great things about a service is that when a feature is ready, we can ship it. So today Office 365 customers will start to see the latest Office Web Apps features. For those of you on the Office 365 Preview, you’ve already had a sneak peek at what’s new. For the rest of you, a refresher on what Office Web Apps are, and highlights of new capabilities beginning to roll out in this Office 365 service update, visible when working with your attachments and documents within Exchange Online and SharePoint Online. What are Office Web Apps? Using browser-based Office Web Apps you can view, collaborate on and share documents, presentations, spreadsheets and notes from anywhere, whether Office on the desktop is available or not. What’s New? For this latest round of updates, we’ve focused on adding editing and formatting controls, consistent co-authoring/collaboration support across the web apps and expanded device support, including touch-enabled editing from tablets . Across the apps, there’s also a clean new look and feel, informed by the updated design language you’re seeing from across Microsoft. In Word Web App , get new support for viewing and adding comments . You’ll also see graphics, images, and layout with excellent fidelity. Format and design documents right from a browser with commonly used features from Word on the desktop, including new page layout tools, picture tools and word count. In addition to comment support, new co-authoring in Word Web App makes it easier to work together on the web. With Excel Web App you get essential spreadsheet features, such as merge cells, context menus, auto-fit columns, formula assistance, fill handle and AutoSum. Manipulate and visualize data for deeper insights with support for high fidelity charts including 3D, improved Query Table and Data Validation support, Slicer functionality and Pivot Chart interactivity. When using PowerPoint Web App presentations look like they do on the desktop, with high-resolution slides, full transitions, and viewable comments. Audio and video playback is now supported, even from a tablet or phone. Drag and drop support makes for easier layouts. While the ability to insert images, apply transitions and animations, or add a pre-designed theme make polished presentations from a browser possible. And new co-authoring and comment support in PowerPoint Web App improves collaboration in the cloud. OneNote Web App updates . Users can find what they need more easily with the ability to search on a page or within a section. And new support for ink viewing makes more information accessible from the web. Just click to type anywhere on the page to add a note, picture or a tag. Notes can now be shared as a URL, viewable on a phone, PC or tablet through a browser. Not only are we delivering new features, but we’ve done some work on the backend to make it easier to update and deploy new Office Web Apps features and services. We’ve decoupled Office Web Apps from SharePoint Online. The two services will continue work well together. However, by deploying Office Web Apps as a standalone service, we can ship improvements when they’re ready, independent of the SharePoint Online ship cycle (and vice versa). Additionally, by serving all of our hosts out of one service center, customers will see more consistency between the Office Web Apps available as part of Office 365 and our consumer service, SkyDrive. In fact, over the weekend the Office Web Apps on SkyDrive hit general availability , bringing the latest updates to consumers within days of our rollout on Office 365. Browser Support Changes As we shared with you this spring, we’re no longer supporting IE7 across Office 365 services . If you are using IE7 with the updated Office Web Apps, they won’t render properly. Update to IE 8 or higher to take advantage of the new Office Web Apps features. That’s just the tip of the iceberg. Want to learn more about new Office Web App functionality? Take a look at  Office Web App Group Program Manager, Mike Morton’s, blog post for a deep dive into the latest features from in Office Web Apps. What? When? Customers may start to see these changes today. As we continue to roll out the service update worldwide, all Office 365 customers will experience all the new Office Web App goodness by the early part of next year.

Announcing MOSDAL 4.6 – The Microsoft Online Services Diagnostic and Logging Support Toolkit

Audience: Office 365 for professionals and small businesses Office 365 for enterprises   With the release of the Microsoft Online Services Diagnostics and Logging Support Toolkit 4.6 , we introduce a number of exciting new features and improve the user experience yet again so both users (information workers) and administrators can collect the right data, for the right problem.  In this release, we made an effort to make the tool and its output, more user friendly.  Not only did we make improvements to the UI to help guide users through the data collection process, we made many of the reports that MOSDAL generates more readable.  Please read below for additional details on all the improvements MOSDAL 4.6 has to offer: User Interface Changes – Added information to help users collect the right data, as well as understand what data MOSDAL is collecting. New Languages – MOSDAL is now offered in Russian and Korean languages. Smaller download – MOSDAL will only download .NET 4.0 and Windows Installer 3.0 if they are not present on the system.  This reduces the size of the installation package by more than half. Exchange ActiveSync diagnostics – In addition to testing the Exchange Autodiscover process, MOSDAL now also performs ActiveSync connectivity tests.  The tests are run sequentially, and the results are now viewable in a web format that is similar to Compatibility with Microsoft Office 2013 and Microsoft Office Click-To-Run – MOSDAL is now aware of and will collect data for Outlook 2013 and Lync 2013.  In addition, if you installed Office 2013 through Click-To-Run, MOSDAL will collect additional data to help troubleshoot Click-to-Run installation and activation issues. Compatibility with Microsoft Windows 8, Windows Server 2012 and .NET 4.5 – MOSDAL will now run without issues on Microsoft Windows 8, Windows Server 2012 and on systems with .NET 4.5 installed. WebDAV ETL component logging for SharePoint Online – Logs are collected by MOSDAL to help troubleshoot issues WebDAV connections to SharePoint Online. Directory Synchronization, Domains/DNS and Exchange Hybrid Configuration reports in XML – Many of the reports generated by MOSDAL are now in XML format to make them easier to read and easier to create automated diagnostics to help identify issues quicker. Windows Network Trace logging – Network tracing utilizes the Event Tracing for Windows (ETW) framework available in Windows. Network components (such as Winsock, TCP/IP, NDIS, packet-capture, and so on) register as ETW trace providers and emit events related to network activity. Any recordable activity of significance can be an event logged to ETW. Tracing for these network components and packet captures can be enabled using the netsh trace context which acts as an ETW controller.  For more information, see . Resources Here are some resources to get started with MOSDAL 4.6: Download MOSDAL 4.6 and the available training MOSDAL Knowledge Base article Here are some additional resources where you can see the tool in action: Exchange Online: 2555008 How to troubleshoot free/busy issues when you use Exchange Federation in the Microsoft Office 365 for enterprises environment 2581088 How to troubleshoot issues that prevent you from viewing other clients’ free/busy information in Office Outlook 2007 and in Outlook 2010 in an Office 365 environment VIDEO :  Troubleshooting Issues with Free/Busy Information in Office Outlook Clients for Office 365 Lync Online: 2566790 Automatic sign-in, domain federation, and other features do not work as expected in Lync Online when you use a custom domain in Office 365Automatic sign-in, domain federation, and other features do not work as expected in Lync Online when you use a custom domain in Office 365 2541980  How to troubleshoot authentication and connectivity issues in Lync Online 2392146  Instant messages to federated Lync contacts fail VIDEO :  Troubleshooting Sign-In Issues in Lync Online for Office 365 VIDEO :  Troubleshooting Instant Message Failures to Federated Contcacts in Lync Online for Office 365 VIDEO :  Troubleshooting “Cannot Connect to the Server” error when using Lync Mobile for Office 365 Office 365 Suite: 2515404 Troubleshoot domain verification issues in Office 365 2621267 How to view and verify CNAME records, MX records, TXT records and SRV records in Office 365 VIDEO :  Troubleshooting Domain Verification Errors in Office 365 Identity federation/Single Sign On: 2598459 How to use the Microsoft Online Services Diagnostics and Logging (MOSDAL) Support Toolkit to diagnose identity federation issues in Office 365 2433327  How to use MOSDAL to enable tracing for the Microsoft Online Services Sign-in Assistant to troubleshoot rich client authentication issues VIDEO :  How to Use MOSDAL to Diagnose Identity Federation Issues in Office 365 Directory Synchronization (Co-Existence): 2643629 Individual Active Directory Domain Services objects do not synchronize to Office 365 2647098 Duplicate or invalid attributes prevent Office 365 directory synchronization VIDEO :  Troubleshooting Duplicate or Invalid User Attributes that Prevent Directory Synchronization in Office 365 SharePoint Online: 2629108  How to use the “Open with Explorer” command and how to troubleshoot issues with this option in SharePoint Online for Office 365 Visit the  MOSDAL wiki page for more information.

Business Data Connectivity Services (BCS) in Office 365 – SharePoint Online

The following video walks you through using SharePoint Online’s Business Connectivity Services (BCS) to connect your line of business (LoB) systems via a Windows Communication Foundation (WCF) service. This allows data from the LoB system on-premises to be viewed and edited within your SharePoint Online environment.   (Please visit the site to view this video)   For more info about BCS, see Notes on Business Connectivity Services (BCS) in SharePoint Online .   Thanks to Manas and Alex from Microsoft Support for putting together this video.   Let us know what you think!   The SharePoint Online Community Team  

Business Data Connectivity Services (BCS) in Office 365 – SharePoint Online

The following video walks you through using SharePoint Online’s Business Connectivity Services (BCS) to connect your line of business (LoB) systems via a Windows Communication Foundation (WCF) service. This allows data from the LoB system on-premises to be viewed and edited within your SharePoint Online environment.   (Please visit the site to view this video)   For more info about BCS, see Notes on Business Connectivity Services (BCS) in SharePoint Online .   Thanks to Manas and Alex from Microsoft Support for putting together this video.   Let us know what you think!   The SharePoint Online Community Team  

New Policy for Inactive Migration Batches

Audience: Exchange Online/Office 365 administrators Author: Ram Poornalingam, Senior Program Manager, Exchange   We’re implementing a new policy for migration batches in the cloud-based service. Active migration batches with a status of “Synced” that have no administrator-initiated activity for the last 90 days will be stopped, and then deleted 30 days later if no further activity is taken by the administrator.   What constitutes activity by the administrator?   Stopping and restarting a migration batch Editing a migration batch by using the Exchange Control Panel or the Set-MigrationBatch cmdlet in Windows PowerShell.   How do we determine if a migration batch is inactive? There is a “Last modified time” property for migration batches, and if the value for this property is more than 90 days, the batch is stopped. If the batch remains inactive for another 30 days (in other words, when the value of this property reaches 120 days), the migration batch is deleted.   This new policy applies to all migration types: Cutover Exchange migrations, staged Exchange migrations, and IMAP migrations.   Why are we doing this? Inactive migration batches consume resources in the Microsoft datacenter. By stopping and then deleting these batches, we can free up resources and help improve the migration experience for customers who are actively migrating mailboxes to Office 365.   For more information about migration, see the following topics on   Manage Migration Batches in Exchange Online Cutover Exchange migration Staged Exchange migration IMAP migration