“Rogue” retention policies in Exchange Online after false positive junk mail is moved to the Inbox

This content is 11 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My Office 365 tenant was recently upgraded to the “Wave 15” version of the service, meaning that my email is now hosted on Exchange 2013, rather than 2010 (Microsoft has provided an article that helps users to understand which version of the service they are on).

Unfortunately, since the upgrade, an awful lot of my legitimate email is getting trapped as junk.  After moving it back to the Inbox, I noticed that one of the items displayed a message about retention policies, highlighting that it would expire in 30 days.

I don’t use retention policies (with gigabytes of empty space in my mailbox I don’t need to), so I thought this was a little strange, until I realised that this was a side effect of having been previously flagged as junk, where there is a retention policy set to remove mail after a month.  I then found that the Managed Folder Assistant (which applies the retention policies) only runs every 7 days on Exchange Online but can be forced in PowerShell.

Sure enough, once I’d eventually managed to connect to Office 365 in PowerShell and run the Start-ManagedFolderAssistant -Identity mailboxalias command, the email was no longer flagged for expiry.

There’s more information on setting up and managing retention policies in Exchange Online with Windows PowerShell on the Outlook.com help pages.

Issues connecting to Office 365 using PowerShell? Check the client firewall

This content is 11 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve written previously about managing my Office 365 tenant using Windows PowerShell (Microsoft has since provided its own documentation on the topic) but I tried today and found that I couldn’t get a connection.

Every time I tried to create a session, the response came back as:

[ps.outlook.com] Connecting to remote server failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved. For more information, see the about_Remote_Troubleshooting Help topic.

+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption

+ FullyQualifiedErrorId : PSSessionOpenFailed

Strangely though, it could resolve the server name as nslookup ps.outlook.com told me:

Non-authoritative answer:
Name: pod51000psh.outlook.com
Address: 132.245.1.167
Aliases: ps.outlook.com

Microsoft knowledge base article 2570535 includes steps for troubleshooting Windows PowerShell issues that affect Exchange Online for Office 365 and suggested

This issue occurs if an internal firewall isn’t started or if the Windows Remote Management service isn’t started

I confirmed that WinRM was running and allowing basic authentication but still couldn’t connect.  So I focused on the “internal firewall isn’t started” part.

Sure enough, the issue was Symentec Endpoint Prevention on my corporate laptop.  I used my wife’s PC instead, and connected with no issues at all…

A toolkit for successful Office 365 deployment

This content is 12 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Over the last few weeks, I’ve attended a couple of Microsoft Office 365 workshops during which I picked up quite a bit of useful information, not least Malcolm Bullock’s (@MBullock) list of Office 365 deployment planning resources.

Office 365 is straightforward: it’s a service; it does what’s in the service descriptions. But successful migration to the service depends on thorough planning.

Of course, this is the point where I should say, “talk to Fujitsu; I’ve got a team of guys who can help you through this” – and I have* but that’s not why people read this blog! What I’ll do instead, is outline some of the resources that Malcolm shared and which should be considered an essential “Office 365 deployment toolkit”:

  • Office 365 Service Descriptions. These are gospel. If the service description says you can do something with the service, you can; and if it says you can’t do it, you can’t. If the information is not there, you probably can’t. It’s binary; black and white – no grey. Office 365 is not for everyone – that’s why on premise and hybrid options exist.
  • Software Requirements for Office 365. Generally, Microsoft gives 12 months’ notice of changes to system requirements but they’re also introducing an n-1 stance on browser support. Bear in mind that, just because something isn’t supported doesn’t mean that it won’t work but using unsupported software is far from ideal and it’s entirely possible that legacy software may be denied access in order to avoid security issues.
  • Office 365 Enterprise Deployment Guide (MODG). Put simply, this describes how to deploy Office 365 in the enterprise.
  • Exchange Deployment Guide (ExDeploy). This is a software tool to run through for on-premise, hybrid or cloud deployments of Exchange.
  • Solution Alignment Workshop. These workshops are professional services, offered by Microsoft and their partners to make sure that the customer requirements are aligned with the Office 365 service. These workshops (together with a number of tools, such as the Deployment Readiness Tool and the Office Alignment Index Calculator) are now being replaced by OnRamp, a streamlined on-boarding process allowing customers to take a staged approach to their Office 365 migration.
  • Test/demo environment. Register for a trial Office 365 tenant.
  • Office 365 Pro Plus Deployment Tool. A tool to configure the click-to-run functionality for local streaming of Office 365 ProPlus desktop software.

There are also many tools and diagnostic utilities referenced from the Office 365 Community website.

* In all seriousness, I’d be happy to discuss Office 365 opportunities with any UK-based enterprises looking at migrating their email to the cloud, or even looking for a hybrid or fully-managed Exchange/Lync/SharePoint solution but this is my personal blog and in no way endorsed by my employer. If you would like a professional conversation, please do get in touch.

Selectively removing cookies to resolve Office 365 authentication issues

This content is 12 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Every now and again, Office 365 decides that it doesn’t recognise my credentials and won’t let me log on. Well, not from a my normal web browser anyway. Everything works on my iDevices, my Windows Phone, even in a a protected browser session (e.g. Google Chrome’s incognito browsing), but not from my “normal” browser, with handy password management extension…

Because it works in a protected browser session, I was pretty sure the problem is related to cookies but removing them all is a bit of a sledgehammer to crack a nut.  Instead, I delete individual cookies by going to chrome://settings/cookies and search for the microsoftonline.com cookies.  After removing these, I can log on successfully for a few weeks until the next time Office 365 decides it can’t authenticate me…

Microsoft’s message to UK partners for FY13 (#PBBBirm #MSPartnersUK)

This content is 12 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I spent most of yesterday at Microsoft’s Partner business briefing in Birmingham. The afternoon workshops were especially good value (I was in the Public Cloud session, learning more about Office 365) but the morning keynote (delivered by Janet Gibbons, Microsoft’s UK Director for Partner Strategy and Programmes) had some interesting messages that are worth sharing further:

  • 95% of Microsoft’s global revenues are generated through it’s channel partners.
  • 2012 is the biggest launch year in Microsoft’s history with almost every product having a major refresh or a new iteration (from Windows 8 to Halo 4).
    • Microsoft is spending significant volumes on product advertising.
  • Microsoft is still a software company, but increasingly a devices and services company.
    • Many of those services relate to software subscriptions.
    • Interestingly, there is a 26% piracy rate for software in the UK (20% of Office users are illegal/mis-licensed) – and no piracy with online services.
    • There are new partner opportunities for selling Office 365 and managing the customer relationship (billing, etc.) to expand the revenue opportunity with value-added services.
  • Microsoft’s FY13 priorities are:
    • Excite customers, businesses and advertisers with Windows 8 devices and applications.
    • Win against Google every time with Office 365 and launch Office [2013].
    • Build application ecosystem for Windows 8, Windows Phone and Windows Azure.
    • Win the datacentre with private, public and hybrid cloud.
    • Grow SQL Server through BI, big data and mission critical [deployments].
    • Drive deployment for Windows, Office, Internet Explorer, Active Directory.
    • Win with business solutions.
    • Grow Windows Phone market share.
    • Drive Xbox profit and grow Kinect and Live Attach.
    • Grow reach, search and monetisation of our consumer online  services.
Interesting to see the Microsoft FY13 scorecard in public: great openness at #PBBBirm - to be applauded #MSPartnersUK http://t.co/AtIlIVNw
@markwilsonit
Mark Wilson

Of course, there was the obligatory Windows 8 marketing message (maybe I’ve been through too many new operating system release cycles and it all feels like another turn on the merry-go-round so I switched off a little in that part) but it was also interesting to hear Intel stand up and say (I paraphrase), “we’re still friends with Microsoft and even though Windows runs on another platform too x86 is better [does anyone remember when Windows NT supported DEC Alpha and ARC-MIPS alongside Intel x86?]. Don’t forget that Atom is power-optimised too [not just underpowered] and we have all this lovely built-in security stuff in our hardware platform”.

As for Office and Office 365 – probably too much for this post but some of the changes coming up in the next release look fantastic. I’m certainly glad I made the switch from Google Apps, although maybe a P1 plan wasn’t the best idea…

Book review: Microsoft Office 365: Exchange Online Implementation and Migration, David Greve/Loryan Strant

This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Every now and again, I get asked to review a technology book. My response is usually something along the lines of “sure, send me a copy and I’ll take a look”. Experience suggests that dead tree editions are more likely to get read than a PDF but sometimes I’m just busy and it takes a while. That’s not because I’m lazy – it’s because if I review a book I want to take the time to review it properly and write a considered response – not just bang out a blog post because the publisher is nagging me for a review…

Unfortunately, this particular publisher was chasing me just 48 hours after they ordered me a copy (and several days before I’d received the book!) and, just a month later (in the middle of the summer holiday season) they are still pushing…

So, here goes. A very short, not very thorough, view on Microsoft Office 365: Exchange Online Implementation and Migration, by David Greve and Loryan Strant (@TheCloudMouth).

As I’d expect from a book written by a couple of MVPs, this book covers all of the basics of implementing the Exchange Online elements of Office 365. Importantly, it doesn’t just concentrate on the enterprise elements, including information for those getting started with the Office 365 plans for small business and professionals, highlighting some important limitations (although not all – as I found recently, the P1 plans don’t include two factor authentication, which is something that users on competing platforms are being encouraged to use).  The book continues to take a logical approach, working through the administration portal and on to integration options – even considering the practicalities involved when the available options from Microsoft are less than desirable,  recommending some alternatives to consider.  Unfortunately the space given to working from the command line in PowerShell (a useful tool in the Office 365 administrator’s arsenal) is very limited.

Moving on through enterprise integration options, preparing for, and performing both simple and hybrid migrations (including supporting infrastructure, such as Active Directory Federation Services), it seems that the authors have covered a variety of scenarios, with many screen shots and diagrams provided to illustrate key points in the process. One criticism is that the screen shots can, in places, feel as though they are being used to pad out the text – presumably the target audience consists of experienced administrators and they shouldn’t really need screen shots of EULA dialogues – after all, this is not “Office 365 migration for dummies”! Finally, the book examines some important post-migration considerations and highlights additional resources.

When I previously reviewed a book from the same publisher, I remarked on the high cover price. Well, I’m pleased to say that this one is a much more reasonable £24.99 ($39.99) and that there are online discounts and free shipping, as well as reasonably-priced eBook options. Indeed, very sensibly, the print and eBook bundle only costs a little more than the print copy on its own.

If you get the chance to read the book properly and you have some comments (perhaps even based on experience of following its advice, as I would have like to have done), then please leave a comment below. Maybe, together, we can crowdsource its review!

Microsoft Office 365: Exchange Online Implementation and Migration by David Greve and Loryan Strant is published by Packt Publishing.

Locating Office 365 invoices

This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Unlike me, who is not VAT-registered and only does his company accounts once a year when he needs to submit a tax return (usually on or around the last possible day…), my wife needs to be a bit more organised and, since she shares the same Office 365 hosting arrangements, I needed to dig out some VAT invoices for her today.  I can never remember how to do this, so maybe blogging it will help me in a few months’ time (and may help someone else too)…

  1. Sign into the customer portal.
  2. On the admin page, on the left pane, under Subscription, click Manage.
  3. Click on the plan name – for me, that’s Microsoft Office 365 (Plan P1).
  4. On the subscription details page click View bill.

If you want to download/print a bill, printable invoices and a graphical billing history are available (links in the top-right corner of the Online Bill portal)

Incidentally, I hadn’t previously noticed that the rate of VAT on my account is 23% – that’s because it’s billed in Ireland, allegedly to avoid* UK corporation tax…

 

*Tax avoidance is legal, even if morally dubious (particularly on the scale at which large corporations work). Evasion would not be

Office 365 administrators: make sure you have these details populated

This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks ago, I wrote about my experience of resetting my Office 365 password/disabling password expiry after I became locked out. At the time I had some issues proving my identity because there was no ‘phone number on file for my account. I had added my mobile number to the user profile associated with my mailbox but that didn’t seem to be what the support team needed.

I’ve since learned that the crucial field is on the technical contact details for the organisation. A Microsoft Support Engineer wrote in an email to me:

“[…] the company information can be changed from the Online Portal. When you sign in and navigate to the admin panel, you should see your organization’s name in the upper left corner. When you click that, it brings up your organization’s information. The global administrator can edit these fields by mousing over them and clicking the small ‘Edit’ button that appears.”

Office 365 administration contact details

Interestingly, since my support incident, Microsoft has introduced self-service password resets for Office 365 but these seem to be reliant on two other pieces of information that are specific to an individual user account:

  • An alternate email address (one that’s not on the Office 365 system – I used a Hotmail account that is also a connected account so I still see service updates in my usual mailbox).
  • The mobile phone field in the user properties (i.e. the one that I had set on my account but which was not the one Microsoft Support were looking for!)
If you are the only administrator for an Office 365 system, it’s worth making sure that these details have been populated.

Logging in to Lync 2010 with the Windows Phone client

This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier today, Microsoft released the Lync 2010 client for Windows Phone (clients for Android, iPhone, iPad and Symbian are on their way).  And, as I’m an Office 365 user and I bought a Windows Phone last week, I decided to take a look.

Installing the app is straightforward enough but I was struggling to log in using the normal credentials that I use for other Office applications (like Outlook Mobile). From looking at the ratings on the app, it seems I’m not alone – with plenty of people saying “it doesn’t work”.

Microsoft’s advice for setting up Lync on Windows Phone is incomplete but the required DNS settings are documented in the Office 365 community wiki.  The missing piece of the puzzle came from Ben Lee – it’s necessary to specify a username (in the format user@domain.onmicrosoft.com) and an External Discovery URL of https://meet.lync.com/Autodiscover/autodiscoverservice.svc/Root.

Once those additional settings were configured, Lync jumped into life!

(For full client configuration details, with screenshots, check out Ben’s post.)

[Update 21 December 2011: It seems this also works with the iOS Lync client, except that also seems to need an Internal Discovery URL before it will allow sign-in (I used the same URL for both internal and external)]

Office 365 password resets… and disabling password expiry

This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My Office 365 account password expired today and, somewhere in the midst of the password reset I managed to lock myself out.  As I only have one mailbox on the account (i.e. I am the administrator), that’s a bit of a problem…

I tried creating a service request to reset my password but I’m not sure it worked – I had no call-back and when I checked later in the Administrator control panel, there were no requests listed; however Dhaval Brahmbhatt (@DhavalBrahmbhat) gave me some UK phone numbers to try (0203 450 6455 or 0800 032 6417).

Using phone support I was able to log a password reset request, once the Technical Support Engineer had confirmed my details.  Because there was no phone number shown on my records, he had to email me so that I could respond with the details. Bearing in mind that I was locked out of my account, this could have been a problem but thankfully Outlook was still connected to Office 365 from my Mac.

After 26 minutes on the phone (at great expense to Microsoft, I guess), I finally had a temporary password to reset my account and then log in as normal.

Goodness knows how I’d have managed if I hadn’t been able to receive an email on the account – although the contact preferences on my Office 365 profile showed a phone number, there was no number in the information for my mailbox… so, lesson number 1, make sure you have a phone number in your mailbox properties (lesson 2 might be to have password resets sent to an alternative mailbox but that seems daft as it’s also where other announcements will end up…).

I’ve decided that I’ll reset my password when I feel like it, rather than when the system says so and making this change involves some PowerShell:

  • First up, install the Office 365 cmdlets (intended for enterprises, not all of them will work on small business accounts). There are two components to install: the Microsoft Online Services Sign-In Assistant; and the Microsoft Online Services Module for Windows PowerShell.
  • Next, connect PowerShell to Office 365 by either opening the Microsoft Online Services Module for PowerShell or opening a normal PowerShell session and typing import-module MSOnline.
  • Authenticate the session by typing Connect-MsolService

(An older method from Office 365 beta can be found in my previous post on changing the primary email address for Office 365 users – I haven’t tested it recently, but I see no reason why the standard Exchange cmdlets wouldn’t still work on Office 365)

  • Finally, disable password expiration with the following command (replacing MicrosoftOnlineServicesID with the appropriate username):
    Set-MsolUser -UserPrincipalName MicrosoftOnlineServicesID -PasswordNeverExpires $true