from the blogosphere article An article written by a former employee of Microsoft’s Azure platform, the TechRadaria blog, has garnered quite a bit of attention over the past week, and has been shared thousands of times.
In the piece, the former Microsoft employee discusses a recent event in which he witnessed Microsoft employees attempting to delete a document in an Azure account that they had stored on the Azure Marketplace.
The Microsoft employee’s account had previously been purchased on Azure Marketplace, but had been deleted due to an issue with the Azure portal’s file upload process.
Microsoft subsequently sent him a message asking for his personal information to be deleted from the Azure platform.
He responded that he had not done so, and that he was not the owner of the Azure account.
He was, however, still able to retrieve the Azure ID that had been purchased in order to store the document in Azure, but only after making some adjustments to the Azure client.
After he had made the changes to the client, the Microsoft employee saw a notification from Azure informing him that the Microsoft Azure Marketplace had been updated to allow for the transfer of documents between Azure and Microsoft’s public cloud provider, Microsoft Azure.
As a result, the document stored on his Azure account was not removed, but was instead transferred to Microsoft’s private cloud provider and subsequently deleted from Azure.
This process was repeated with the same Microsoft Azure account on two other public cloud providers, Google Cloud and AWS, as well as with an account belonging to a third public cloud service, Google Compute Engine.
While the process of transferring files between Azure services has been fairly well documented over the years, there have been some interesting discrepancies in how the transfer is carried out.
For example, some of the documents stored on Microsoft’s cloud providers have not been stored in the same database as the Microsoft cloud storage account.
Other documents stored in Microsoft’s storage account have not also been transferred to other providers, nor has any data been stored on Azure in those instances.
Some of the data that has been transferred is not actually in the Azure storage account, but in an external database that is not in Azure.
The transfer of these data to Azure’s internal storage account also appears to be somewhat arbitrary.
In an attempt to verify whether or not the process actually takes place, the author conducted an analysis of the files transferred to Azure, as the process is not explicitly documented in the documentation, and therefore it is unclear whether the transfer was actually carried out in a formal manner.
While he did not attempt to confirm that the transfer actually took place, he did note that the document transfer was conducted without the knowledge of the customer, and so was not in compliance with Azure’s storage policies.
In a separate blog post from the same author, Microsoft confirmed the existence of the transfer process, and stated that it is an automated process that takes place every 30 days.
However, Microsoft did not provide any indication of how the process was carried out or how many Azure storage accounts were affected.
In its statement to TechRadaries, Microsoft explained that the process, which is also referred to as a transfer, is conducted when the user creates a new Azure storage environment and then creates an Azure ID.
The Azure ID is then used to create Azure resources on the Microsoft public cloud.
The process then creates a copy of the existing Azure resources, using the user’s own Azure ID, in the new Azure environment.
Microsoft’s statement further stated that Microsoft’s internal Azure storage is not affected by the process.
However to prove the process does actually take place, Microsoft’s customer service representative contacted the author and asked him to provide proof of his Azure ID creation.
Microsoft provided the author with a Microsoft Azure ID from its own cloud storage.
While Microsoft’s own internal Azure cloud storage is located in Europe, Microsoft has also distributed its own Azure cloud-based storage to customers in North America, Asia, and Australia, as shown in the following table.
Microsoft Azure storage (in GB) Storage Provider North America Europe Australia Google Comp.
Cloud AWS Microsoft Cloud Amazon EC2 AWS (UK) Microsoft Azure (US) Amazon EC3 AWS (US/NZ) Amazon Elastic Compute Cloud Microsoft Azure S3 Microsoft Azure Compute Service Microsoft Azure EBS Microsoft Azure Azure (EU) Microsoft S3 Azure (Europe) Amazon DynamoDB Amazon Elastic MapReduce AWS (Canada) Amazon CloudFront Amazon Dynamo DB (US and UK) Amazon Redshift Amazon Elastic Blockstack Amazon Dynamo DBD Amazon Elastic Stack Amazon Elastic Load Balancer Microsoft Azure DynamoDB (US & UK) Microsoft Cloud Datacenter Azure Datacron AWS (EU & UK), AWS (AU) Amazon Web Services Azure Web Services (US, UK & AU) Amazon Route53 Amazon Route 53 (US), Route53 (AU, NZ, AU) Microsoft Datacore Azure Datacenters (EU, AU, NZ) Amazon Glacier Amazon Glacier (US / NZ) AWS S3 Amazon Glacier Service (UK & AU / NZ, US, NZ / AU