Graph created OneNote not recognized as "Site-Notebook"
When creating a new Office365 Group, the "Site Notebook" is not provisioned until the Notebook link is clickedin the left navigationof the associated SharePoint site. I'm trying to automate this process by creating the Notebook through the GraphAPI (/groups/{id}/onenote/notebooks) - which works fine. However, the newly created notebook is not coupled to the navigation link in the left menu of the SharePoint site. This results in asecond notebook being created when clicking the link. Is there a way to indicate that the notebook I created should be used as theSiteNotebook? PS: I also noticed that Notebooks are created in Shared Documents library, and the "default" one in SiteAssets.Scheduling a meeting for a group - OneNote meeting notes
When I schedule a meeting for an Office 365 group with Outlook 2016 desktop, I want to include/associate meeting notes in OneNote. I assumed that clicking on the OneNote icon in the meeting request ribbon would allow me to specify the notebook associated with the group - but it doesn't. In fact, the notebook with the group isn't even accessible as a choice in which to create the notes. As it turns out, this is a new group and a new notebook which has never been used before, and I find that I have to open it locally in OneNote desktop first before it is ever seen as a choice of target notebooks in my group meetings. This doesn't seem right - and is confusing the heck out of my users who are just now getting into using O365 groups. Can anyone confirm/validate that this is what they are seeing as well. The workaround is obvious - but very inconvenient. Thanks, BobPeriodic Table of Office 365 is now dynamic and web-based
The Periodic Table of Office 365 is now web-based, clickable with app descriptions, available in seven languages, and embeddable. That's right, you can have a live version right in your intranet or website -- just like what you see below! Check it out and make sure to give us feedback. (Just remember, it's in BETA.) Never heard of it? This graphic is a popular resource for explaining WHAT Office 365 is to IT, users, management, you name it. You can't talk about something if you can't define it, right? [details | full-size version| O365 Groups infographic]OneNote Search Scope in SharePoint for Office 365 Groups
Hi All, I'm trying to figure out the default indexing and search scope for the SharePoint Team Site that is created with an Office 365 group and how it works with OneNote. I haven't found a lot of documentation, butwas experiencing some issues. The actual OneNote page isn't returned when searching for terms in that page, however, the first page of a section is returned. For example, If I have a section called Section X with three pages, Page A, Page B and Page C and the term I am searching for is in Page C, Page A is returned in the result set. Some screenshots below. Is there documentation I might be able to find? See screenshots for example. Onenote Search Term https://www.screencast.com/t/FGGf2OAVoe Searching for term https://www.screencast.com/t/Un2f42XSQd Result is Page A, instead of C. https://www.screencast.com/t/NccP9UpQIz6 https://www.screencast.com/t/eV44bVmiKOffice 365 Groups with Dynamic Membership - Support in Outlook Desktop 2016
We are using Office 365 Groups with Dynamic Membership (Azure AD Premimum). These Office 365 Groups do not appear in Outlook Desktop alongside Office 365 Groups that have Assigned Membership. Outlook Desktop Cached Exchange Mode is enabled for all users. We are in an Exchange hybrid envirnoment. Any suggestions to get this working or is this not supported? I cannont find any documentation stating one way or another. Are Office 365 Groups with Dynamic Membership supported with Teams, Planner, OneNote, etc. ?Inconsistent naming for OneNote
We experience inconsistent naming for the Notebooksrelated to an office 365 group. So far we have three different cases. None of these names were changed manually. When opening such a notebook inthe OneNote desktop version the name of the notebook can be: - "Notebook" which is the worse,because you have to go through each of them before you can identify the correct one. - "Notebook" + group-id (which is also used in the url of the team site) - "Notebook" + group name I suspect it is related to the way the group was createdbut I hope this will become consistent in the near future! BartExperiences "migrating" to an O365 Group
So, I am starting to "migrate" the particular team that I work for over to Groups (that means from our existing SharePoint site, existing Yammer group, existing mailboxes, etc). Wanted to share the general experience and reception so far, with PLUS / MINUS perception notes: PLUS - We are looking to use Group Conversations and shut down use of Yammer for our team discussions. So far users seem more apt to use the conversations because it is more like email, so probably a ding for use ofYammer In general we are going to guide Groups users away from using Yammer PLUS - We are using an automatic group membership (everyone that reports to my Manager) - which works perfectly! We have a revolving door of interns/temps as part of the team, and access to resources is no-brainer. MINUS - This will be our first Modern SharePoint site, and big negative is critical links removed from the UI. Menu - using "/_layouts/15/AreaNavigationSettings.aspx" to recreate our horizontal navigation. This accomplishes what we need, but I fear that it may eventually go away... Permissions - I understand group permission limitations, but our connected SP sites have to have additional viewers and contributors. Right now from the UI, can only apply permissions to Group Owners and Group Members. Using "/_layouts/15/user.aspx" to get around this for now, but again will future updates restrict this? MINUS - Document Migration - we have our own PowerShell scripts that we use to migrate content between sites. The scripts appear to only work run by a Group owner if the person running the script is a Group owner. We typically use a service account and set it as Site Collection Admin, run the move, then remove the service account. Here the service account still doenst have rights even after being made the SCA for a Group. We will definitely be doing most of this for our users since we don't want to put the tedious actions on them MINUS- Calendar - we use a SharePoint Team Site calendar - was able to easily open the SP Calendar in Outlook "Agenda View", copy entries, and paste them into the Group Calendar (in Outlook Agenda View), but they never synced back up, never appeared in the Group calendar, though I see them in my physical Outlook calendar Dont seem to be able to create just an entry (without actually inviting all attendees) MINUS - Group Navigation - switching between the different Groups workloads is still pitiful I've manually entered direct links to the different workloads in the Groups SharePoint Site, but users continually get "lost". They'll end up on the calendar which has no links whatsover (sometimes), the options are in different places in each workload. I know this has been brought up over and over, but its been months and months, if not over a year at this point, and doesnt seem this is getting any better at all. MINUS - Groups files - this is maybe just our opinion, but do not like the Groups Files automatically including email attachments in the default view. Often confusing, especially if things have been moved to the SharePoint files, you see duplicates, etc. PLUS - Groups app - easy access to everything, general consensus is much easier to find stuff from the app then from the web itself MINUS - Groups app notifications - marking conversation messages as read seems to be wonky, users are complaining because they have to physically leave the group a couple times before it tells them they have read all the messages. MINUS - Planner - Though there is excitement about what Planner can be, some negatives emerging - no Planner app, unsure of a way right now to move items from a SharePoint Action Items list to Planner (other than just manually reentering stuff). PLUS - OneNote, this has always been my favorite thing Microsoft has built, so glad to see it easier integrated into our group activities. We are migrating our running Staff Meeting Agenda (from Yammer note) to OneNote MINUS - UI - we have always used a custom enterprise mega menu throughout our SharePoint environment, for easy navigation, with no customization options, we lose this and will have to start teach our users to keep going to our Intranet homepage, then navigate where you want to go with the menu NEUTRAL - Dont care for the single column of the websites, we have traditionally used a custom responsive layout that has at least 2 columns of content. Everything just feels to big / too much whitespace. MINUS - SharePoint App, we have multiple document libraries, the Groups/SharePoint apps really only focus on the primay Shared Documents one. Overall, it seems like it will be a positive adoption, but there are several things that just miss the mark, at least for how our organization works.