I'm also seeing the same error code this morning. The error is being reported within Microsoft Community Forums, so it appears to happening frequently this AM.