O365 access for students

[reprised]

Hi everyone,

 

I hope you're all enjoying a good summer and are not too overwhelmed with work. We are setting up office 365 education for our students and staff and was wondering if those who have been using it can advise what if anything you lock down for students. For example do you allow students to search for and email staff. Do you allow emails inbound to students from anyone or just certain domains? Currently they have Mail, Calendar, People, Newsfeed, Onedrive, Sharepoint, Planner, Tasks, Delve, Video, Sway, Forms. I would be interested in knowing what others do and sorry if this has been asked before but couldn't find a similar thread

 

[nadeem]

I think it would depend on what type of educational establishment you work in - I work in a university so my students are all 18+, I would probably do things differently in a school for exmaple.

[dapaulio]

We only use o365 for office and onedrive with our email remaining an on site exchange.

 

The only blocks we impose on student is emailing the staff distribution group

Edited August 2, 2016 by dapaulio

[CapnPugwash]

All our staff are on O365 & we will slowly start to migrate students over in the new academic year. The theory is that we will start with the new year 7's, give it a couple of weeks, see what mayhem they have caused and adjust our rollout plans accordingly.

 

There are other threads that cover this topic, not sure if I've seen anything that groups everything together.

 

I know other people have raised concerns about student access to Yammer, Skype etc.

[gaz350b]

With office365 I would initially restrict via licences and add them as and when you need to. You need to satisfy senior leaders that you are able to respond to any safeguarding issues when using these services, so before enabling anything ensure you have a process in place to access things like onedrive, yammer etc.

 

also be aware of office365 groups and planner as students by default can create their own groups.

 

Also be quick at evaluating new features so monitor your admin feed on a regular basis.

 

One last tip.

 

Plan your changes in active directory carefully do not rename OU's. Create new OU's give it time to sync then move users in small batches testing between syncs. Give active directory and the sync tools lots of respect and time to process changes.

 

My techie decided to clean up the staff ou and renamed it for some reason and it caused all the staff accounts to delete in o365!! We are still getting some randomness 3 weeks on but are getting through them slowly.