OneDrive for Business on Office 365 Never Enables
-
Can you sign into https://login.microsoftonline.com/ with your 365 account?
-
@DustinB3403 said:
Can you sign into https://login.microsoftonline.com/ with your 365 account?
You mean the NEW account that isn't the useful one that we've established I'm logged into since I get the message that it isn't setting up ODfB and doesn't have my data?
Or the old one that doesn't exist?
-
The site supports two different login's one for a business account and the other for a private account.
-
Here is what Delve shows. Clearly things are not working.
-
@DustinB3403 said:
The site supports two different login's one for a business account and the other for a private account.
I don't have either.
-
Newsfeed is not working...
-
@Carnival-Boy said:
What do you mean Microsoft lost your old account? That's sounds extremely serious.
There was a billing issue (right or wrong is not my place to know) and the account was terminated.
There was never an outage of Azure services no matter how Scott wants to phrase is to push blame.
Were services that Scott was offering/using down because of said account terminating? Yes.
Was there a failure? Yes, but it wasn't Azure or OBfB or Exchange Online or any other component. It was an account level failure.
Was it Scott or Microsoft? Dunno. -
I have to ask, as I've seen it happen a few times.
Open an incognito tab if your using Chrome and attempt to sign in using your business account.
-
@JaredBusch said:
There was never an outage of Azure services no matter how Scott wants to phrase is to push blame.
Were services that Scott was offering/using down because of said account terminating? Yes.There wasn't a billing issue, there was a backend technical issue that caused an account to be lost.
So services were down but that's not an outage? I don't see how it can be one or the other. Azure was unable to deliver services, that's an outage. That it was triggered by a technical glitch on their account system rather than in the hypervisor isn't relevant and is misdirection. The platform itself failed (isolated to one account family) and was technically unable to host VMs and had an outage.
Even after the issue was identified to be an account-related one, MS was unable for many hours to even begin to figure out how to spin up VMs to recover from the outage. It was an outage, plain and simple. It was a technical failing of the Azure systems and a fragility that was built into the system and a lack of clear support issues was the cause of the ongoing outage.
The outage was not isolated to OUR account, but happened in a rolling manner to many other accounts, including to others in this forum.
How do YOU define outage if it isn't that the ability to deliver your product to your customers? Redefining it as only certain types of technical failures and not others seems misleading. It's not my place to care why Azure failed, that's MS' problem. It failed and require a lot of escalation, a lot of pressure and many engineers and managers to restore it within half a day.
-
@JaredBusch said:
Was there a failure? Yes, but it wasn't Azure or OBfB or Exchange Online or any other component. It was an account level failure.
Here is the question, why does this matter?
This is just a way to make excuses. A bunch of systems do not work: ODfB, OneDrive, email (now fixed), Azure (now fixed.) Data loss, outages... that they happened because of the accounting system or a power loss doesn't matter.
Try telling your customers that they didn't have an outage when their systems go down because you don't consider you aren't down. That's not how this works. Microsoft's systems stopped working because of issues on their end. The applications that they provide stopped working. That's an outage.
-
@JaredBusch said:
There was a billing issue (right or wrong is not my place to know) and the account was terminated.
Just FYI, Jared is talking about an unrelated issue with an Azure outage two weeks ago. Nothing to do with this account or system which was never terminated or anything of the sort. This account was never suspended, canceled or anything and there was never a billing issue. Nothing of the sort.
This is an older issue from a month ago, long before the unrelated Azure issue took place.
-
@JaredBusch said:
Was it Scott or Microsoft? Dunno.
Unlikely to be me as I'm an end user of both systems and don't control the accounts, billing, setup, etc. I'm just a customer experiencing a loss of functionality and/or data depending on the situation.
-
@DustinB3403 said:
I have to ask, as I've seen it happen a few times.
Open an incognito tab if your using Chrome and attempt to sign in using your business account.
There isn't a problem singing in, my profile doesn't exist properly. MS has escalated now and should have support online in about half an hour.
-
MS Engineering is looking into it now.
-
@scottalanmiller said:
Here is the question, why does this matter?
Systems are down, yes. It is a failure, yes. Azure is not down, no. Azure is down to you, yes. It is a Microsoft outage, yes.
It matters to be precise. You of all people should understand that.
What would I tell my clients if this happened on my account? I would tell them there was some kind of MS problem with the account causing the services to go offline. This is the fact. I am not trying to push it off as not an outage. I am stating clearly WHAT it down. It makes all the difference in the world.
-
@JaredBusch said:
I am stating clearly WHAT it down. It makes all the difference in the world.
Right, and what was down to us and our clients was Azure. It's not like only our VMs were offline, MS themselves were unable to spin them back up.
If Azure has a full site go down, we don't say it isn't an outage because other sites are up. All outages have a scope. This was just as much an outage as any other type, the scope was just account related rather than geographically related. Still an Azure outage. It was not a complete Azure outage of all accounts and/or all sites. But even internally at MS the platform was down for our account and could not be restored. Not like it was an outage on our end, the outage was totally at the Azure end.
-
@JaredBusch said:
@scottalanmiller said:
Here is the question, why does this matter?
Systems are down, yes. It is a failure, yes. Azure is not down, no. Azure is down to you, yes. It is a Microsoft outage, yes.
It matters to be precise. You of all people should understand that.
What would I tell my clients if this happened on my account? I would tell them there was some kind of MS problem with the account causing the services to go offline. This is the fact. I am not trying to push it off as not an outage. I am stating clearly WHAT it down. It makes all the difference in the world.
This is completely unrelated to the crossed-account billing issue with Azure. That was a MS Azure internal issue, and we were completely at their mercy to get it straightened out: not our issue. This is a MS (not Azure, which is totally separate) account problem. I don't think blame is necessary here, but MS' support attention and abilities are being called into question.
-
MS just managed to recover my old data. They are monitoring the ODfB setup issue now to see why or where it is stalling to see what can be done.
-
I'm chiming in a bit late here, but there are a lot of missing data here. This thread reads like an end user (no offense Scott, you know I love you lol) posting in an IT-peer forum to help solve their problem when the Administrator of the service is kept out of the loop on the thread - so much missing information.
Information such as:
-
Who is administering this account? We need a global admin on the tenant involved here for that Office 365 tenant. Is that you, Scott? Do you have that level of access in the tenant? What subscription do you have assigned to that user account? Is this a "business" account (e.g. Enterprise E1, E3, etc...)?
-
What type of account are you using to log in? Is it a DirSync account? Is it a pure cloud account?
-
In regards to the lost email and such - that is completely unacceptable and actually makes no sense from an admin standpoint, at least based on my knowledge and past experiences. For example, If I remove a user (i.e. stop syncing them, in the case of DirSync), it removes the account, but the email and corresponding SharePoint\OneDrive docs is still on that tenant for (I believe) 30 days and is totally recoverable either by re-syncing the account and assigning a license, or by contacting Office 365 support and working with them (I have worked with Office 365 support MANY times and have had much success with them - your experience is not typical and I am actually very surprised by it). In fact, if the user is set up properly in Active Directory and has an assigned manager, that manager is emailed automatically to let the person know that the terminated employees resources are available for review. There are also indefinite archives (and it doesn't count against any storage - it's quite slick actually). I have rules set up so that I have the email of every single employee that ever worked here, even if their account is long gone. I can download a PST of that user's email at a whim.
-
In regards to your current issues with OneDrive not provisioning - again, this is something that needs to be looked at by Office 365 support, which, if you have valid subscriptions, should be more than available to help. If a tenant service (like OneDrive for Business) isn't provisioning properly, that means something happened at a higher level that needs to be looked at by MS technicians.
-
-
@scottalanmiller said:
MS just managed to recover my old data. They are monitoring the ODfB setup issue now to see why or where it is stalling to see what can be done.
Now THAT makes total sense!
