jamesbmarshall

This is one of those times where I wish I'd bookmarked the page where I saw this information... I think there is/was a bug if you used ABPs and hiding from address lists together which caused some interesting routing issues but I can't put my hands on the page now! Log a service request. EDIT: Found it! See the response from Greg Taylor: Exchange 2013 Address Book Policy Routing Agent Issue with Mailboxes Hidden From the Address Lists

It's all in the service descriptions Office 365 Service Descriptions

Yes @funkyfin2000 that's exactly the post I'm talking about. I'd forgotten that I'd written that! I'm glad someone reads my blog... The advantage of PALs is that you don't become responsible for managing the credentials of that identity - that's left with the end user. Of course, the subsequent disadvantage is that they must be managed manually, and for lots and lots of parents this can quickly scale to be a time consuming overhead.

Don't forget that, under A2, you get 50GB inbox and 50GB archive for free. You just need to turn the archive on, and set some policies. It depends on your requirements. If you just want to offer a "best effort" archive for emails for a period of time then you could just use the free archive features, turn single item recovery to the full 30 days free. After 30 days this would not stop mail being permanently deleted, but at least you'd have a process for automatically keeping stuff. If, however, your requirements are that you must keep mail for a mandated amount of time (let's say 7 years) to comply with FOI requests or whatever might come your way, then you could invest in Exchange Online Plan 2, as I mentioned previously. This allows you to extend your single-item recovery beyond 30 days, and also allows you to put mailboxes on litigation hold. I would definitely not recommend PST files. That is a world of problems waiting to happen. If you just want somewhere to shove mail that's safe and anywhere-that's-not-my-inbox then I'd give the online archive a go and see how you get on.

Parent access to SharePoint can be achieved using the Partner Access Licences (PALs) that are available. Providing parents with a licensed user account, for any workload, is not a scenario we currently support but, as ever, feedback is heard loud and clear. Believe it or not, engineering a suitable solution to this kind of problem is not straightforward and even if Microsoft supported parents (not saying it won't ever, but it doesn't right now) actually managing them is a big consideration for the school. In fact, I'd say that it could end up taking more time to manage than students and teachers. For example, a student user is provisioned and as long as there are no issues with the student you can pretty much forget about that user object for its life in an ideal world. With parents you have to be concerned with who has access to what data, what happens when families come together or worse, split up, etc. some of these situations can change day by day! Equally, if you don't use the PAL route then you're responsible for password resets - how would you manage those? Would parents phone up the school and request a reset or would you go down the route of providing some kind of self-service password reset portal? Unless you deploy something like ADFS to manage access, and therefore keep your parent user objects in AD, you're going to have to manage them separately via Office 365 (an overhead). Bit rambly, but it's Friday afternoon. Food for thought. Like I say, feedback good. Heard. Fed back.

The A3 plan offers a lot more than just the unlimited mailbox and archiving features. It also includes the Office ProPlus subscription and other little enhancements. If you're specifically looking for longer rolling legal hold then you could look at just purchasing the Exchange Online Plan 2 component and giving that to the users that require it. This is also another option; if you've got on-premises or other hosted storage then you can do this without Exchange Online Plan 2 or A3. Exactly this. You can have (for example) your students on A2, your "regular" teaching staff on A2, and your admin staff, SLT, etc. on A2 + Exchange Online Plan 2 or A3. Basically you can assign licences to whichever users need the functionality. I'd say that it would be a pretty unusual requirement to need to keep student mail for 5 years; perhaps the 30-day single item recovery is enough for them?

Sorry @sukh but the upgrades can't be pulled forward.

The best thing you can do is to disable activities in the Newsfeed, but you can't turn it off completely. I know this isn't perfect - feedback is heard loud and clear! Believe me, it does.

Do you mean changing it from something.onmicrosoft.com to somethingelse.onmicrosoft.com? If so, then I can save you some time, because unfortunately once it's set when you first sign up, it's set for life. The only way to change it would be to start again from scratch in a new environment. Of course, you can add your own custom domains in as you need them but the .onmicrosoft.com bit (aka the MODRD, or MOERA) can't be altered.

Have you set their UPN in AD to be their new username?

The vast majority of upgrades will be completed by the end of September, but it's a huge task and some upgrades may spill over into October.

Yes, in my opinion, a shared mailbox would be better. Then you can use some of the guidance talked about here: Office 365 technology - Configuring delegate access in Outlook Web App to help configure sharing out, and delegation. Better to use a shared mailbox that someone's personal one as people move on / roles change.

In the latest version of Office 365 you can manage calendar permissions from within OWA; including where meeting request information gets sent as a delegate admin. This blog has some pointers: Office 365 technology - Configuring delegate access in Outlook Web App

Yes, it's possible to specify a different primary SMTP address to UPN; but the UPN in Office 365 must match the UPN in AD. So you could have [email protected] as the login name, with a primary SMTP as [email protected]. In the proxyAddresses attribute in AD, add multiple addresses prefixed by "smtp:", and "SMTP:" for the primary. For example you'd have a UPN of [email protected], and then proxy addresses: SMTP:[email protected] smtp:[email protected] smtp:[email protected] Make sense?

You should receive a date soon if you haven't already. Feel free to PM me with your .onmicrosoft.com domain name and I'll see if there's any further info. Before everyone bombards me I'm not able to provide much insight into dates if you've not already had yours. We usually only know when you know (or not long before). Best bet is to check your admin portal for info if you're not getting the emails.

I hear this a lot, but I don't think it needs to be as bad as people think. For example, you could welcome everyone back to school (or just "to school" for new starters ) with an email saying that in 'x' amount of time they'll see some big improvements coming to their inbox, and then provide them with some links to find out more, such as some of the resources here: Resources for Users and Power Users - Upgrade to Office 365 - Office 365 - Microsoft Office 365 Community, like: What's new in Outlook Web App - support - Office.com. Change doesn't have to be confusing, and I know first-hand that people don't read so you can't guarantee the effectiveness of the email campaign but it is a start. Why not sign-up for a second environment that you can use to make some screencasts or blog posts or other internal comms walking through the latest changes in the context of your school? Hold a competition for your students to submit their best top tips for the new update? I'm just throwing a couple of ideas out there, not saying they're good. But hopefully you can see there are ways to make a transition easier. How do other schools manage change with their users? What campaigns do they run? I'd love to know of any really successful stories, maybe they can be re-told on our blog!

I love your enthusiasm but no, sadly you're scheduled a date and unless you choose to defer once, that's it.

That's the major positive, or negative, about moving to the cloud though (with almost any provider, not just Microsoft). Over time I'd expect the notion of an upgrade (in a majorly disruptive sense) to become a bit passé, and things will just evolve.

If you've used your option to defer it once then there's no way to change it.

The "cloud" does not mean you lose your job, not usually. I used to hear that a lot a few years ago. "Cloud" services don't run themselves. Granted, whoever provides the services keeps the lights on, the power running, the patches patched and the air con cool, but ultimately you'll still need to keep your skills in managing these services* up to date. You can't just "set and forget". Not for very long at least. *You just might need different skills of course... If I'd had the chance to ditch my (super capable but ultimately time consuming) Exchange org in favour of letting someone else do the hard work so that I could focus on other more important things I'd have been all over it!

The best way I can think of to do this is to go down the route of ADFS; then you can use the logon hours in AD to restrict when users can authenticate. I agree with @elsiegee40 though, the better way to handle this would be by encouraging better work/life balance practice rather than trying to architect something complex. Still, if the HT wants a technology solution then ADFS is the best way. Trying to actually stop mail delivery is only going to negatively impact both you, and the people who try to communicate with you, in the long term.

If you have more than 50,000 objects in your local AD (that's objects, not just users - run the deployment readiness tool to determine the number) then you should contact Microsoft Support to get your DirSync object limit raised. As you've come from Live@edu did you run the preparation scripts as part of the upgrade? (Assuming you were using ILM beforehand)

This isn't the default behavior - do you have any scripts running to assign licences after provisioning? By default, user objects have no services provisioned against them until you go and assign a licence. Not really (by which I mean not easily, or in a supported manner!). Once you tie your Office 365 tenant to your AD for that particular domain namespace it will always defer to the local AD for changes to user objects. If you don't want user objects in the cloud to receive certain workloads then remove the licences assigned to them; or remove/filter them out in the AD.

Do you actually want to stop email from being received to the mailbox, or just to stop people from logging in to access it? Stopping mail from actually getting to it outside of working hours seems pretty drastic... what would you want to happen to inbound mail? An auto-response? An NDR? Silence?

...and beyond! Up to 100GB. [h=3]SkyDrive Pro storage increases making it even better for storing and sharing class work[/h]