SharePoint Embedded: Coming Soon to a City Near You
SharePoint Embedded, the AI forward platform that lets you deliver Microsoft 365 document capabilities as part of any app, has been generally available for a year, and we are excited to see the many projects people are building with it. In celebration, we are increasing our investment in your success with enablement focused city tours, a total of seven more in-person hands-on education opportunities, this June. SharePoint Embedded is a new way to build a new kind of app, an AI forward platform for document centric apps, delivering rich Microsoft 365 capabilities like Microsoft Copilot AI, Microsoft Office collaboration, Microsoft Purview security and compliance, and a whole lot more. SharePoint Embedded can help you build both enterprise line-of-business apps and ISV apps, on any platform. Space is limited, so sign up today here. Our planned stops include: June 9, London June 11, Stockholm June 13, Madrid June 23, Chicago June 25, Atlanta June 27, Houston June 30, New York These half-day tech focused enablement sessions are designed for IT leaders, product owners, enterprise architects, and senior developers who want to get deep into how they can benefit from SharePoint Embedded. We’ll cover SharePoint Embedded essentials, AI agent development, Microsoft 365 integration patterns, one-click Office collaboration setup, and Purview capabilities. Plus, we’ll also get hands on with the technology, so you can see it in action yourself.
Teams app is crashing if window.location.hash it set
We are using the Teams Channel Tab app with a component that replies on the hash parameter. On click of a button from a list of folder within the Tab, we are trying to set the window.location.hash. Another component uses an event listener to listen to the hashChange and retrieves this hash parameter that was set and uses for further processing. This works perfectly fine in Outlook addin as we are rendering the same component in Teams and Outlook However, as soon as I set the window.location.hash, the app crashes without any error in Developer tool Console. We have hosted the Tab app at - "https://localhost:8080/#/channel" I am thinking of 2 possible causes for this crash- 1. Is the app trying to crash when I am setting the hash as it already has '#' in the url? 2. Is there a limitation where we cannot set and get window.location.hash while inside the Teams Tab app?
Changing monitor input causes windows to maximize over taskbar.
I have this issue when changing inputs on my monitors. When going from my work computer to my pc, my pc will adjust all my windows to maximize over the taskbar. When using this browser for example, it appears as if my taskbar is hidden. However, I do not have the taskbar on autohide. If I minimize the window my task bar appears as usual, as it should. Any window (browsers, spotify, discord, etc...) that is maximized covers the taskbar. The only work around I have found for this is by adjusting the display resolution, and then reverting. Something about the temp resolution change causes the functionality to return to normal. I have ran all updates and cannot find anyone that has reported similar issues.Outlook Deeplink opens a email compose window in draft state only for the first time
I am using the Outlook compose deeplink to open a new email in compose window from my react application with window.Open(deeplink), however for the very first time a new browser window is opened with new email in Draft state. If I use the same compose deeplink again from the same browser, then it opens the new email in compose mode as expected. It feels there is some issue with the cache/cookie storing the OpenID Connect token that gets loaded when I open outlook with the deeplink for first time, and other times it opens the compose email window properly. Also when I already have Outlook opened in browser and then if I open new browser window from my React application using the deeplink, it works alright. Deeplink - https://outlook.office.com/mail/deeplink/compose/...
OneDrive usage reports return GUIDs or pseudonymized values instead of actual data values.
OneDrive usage reports and Graph API endpoints /reports/getOneDriveUsageAccountDetail started returning GUIDs for ownerDisplayName, ownerPrincipalName, and siteURL instead of the actual data values that had previously been returned. This is an expected behavior, which was implemented starting Sep 1st, 2021.
