[stg] article owner tamram > marsma

articles/storage/storage-configure-connection-string.md

@@ -3,8 +3,8 @@ title: Configure a Connection String to Azure Storage | Microsoft Docs
 description: Configure a connection string to an Azure storage account. A connection string includes the information needed to authenticate access to a storage account from your application at runtime.
 services: storage
 documentationcenter: ''
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: ecb0acb5-90a9-4eb2-93e6-e9860eda5e53
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/16/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 
 ---
 # Configure Azure Storage Connection Strings
@@ -54,8 +54,8 @@ For example, your connection string will look similar to the following sample co
 
 > [!NOTE]
 > Azure Storage supports both HTTP and HTTPS in a connection string; however, using HTTPS is highly recommended.
-> 
-> 
+>
+>
 
 ## Create a connection string using a shared access signature
 [!INCLUDE [storage-use-sas-in-connection-string-include](../../includes/storage-use-sas-in-connection-string-include.md)]

articles/storage/storage-custom-domain-name.md

@@ -3,8 +3,8 @@ title: Configure a domain name for your Blob storage endpoint | Microsoft Docs
 description: Learn how to map a custom user domain to the Blob storage endpoint for an Azure storage account in the Azure Classic Portal.
 services: storage
 documentationcenter: ''
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: aaafd8c5-eacb-49dc-8c8b-3f7011ad5e92
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/17/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 
 ---
 # Configure a custom domain name for your Blob storage endpoint
@@ -23,8 +23,8 @@ You can configure a custom domain for accessing blob data in your Azure storage
 
 > [!IMPORTANT]
 > Azure Storage does not yet support HTTPS with custom domains. We are aware that customers are interested in this feature, and it will be available in a future release.
-> 
-> 
+>
+>
 
 There are two ways to point your custom domain to the blob endpoint for your storage account. The simplest way is to create a CNAME record mapping your custom domain and subdomain to the blob endpoint. A CNAME record is a DNS feature that maps a source domain to a destination domain. In this case, the source domain is your custom domain and subdomain--note that the subdomain is always required. The destination domain is your Blob service endpoint.
 
@@ -62,7 +62,7 @@ is the same. Note that many basic domain registration packages do not offer DNS
    provide a host name, which is your Blob service endpoint, in the format **mystorageaccount.blob.core.windows.net** (where **mystorageaccount** is the name of your storage account). The host name to use is provided for you in the text of the **Manage Custom Domain** dialog.
 8. After you have created the CNAME record, return to the **Manage Custom Domain** dialog, and enter the name of your custom domain, including the subdomain, in the **Custom Domain Name** field. For example, if your domain is **contoso.com** and your subdomain is **www**, enter **www.contoso.com**; if your subdomain is **photos**, enter **photos.contoso.com**. Note that the subdomain is required.
 9. Click the **Register** button to register your custom domain.
-   
+
 If the registration is successful, you will see the message **Your custom domain is active**. Users can now view blob data on your custom domain, so long as they have the appropriate permissions.
 
 ## Register a custom domain for your storage account using the intermediary asverify subdomain
@@ -85,7 +85,7 @@ The asverify subdomain is a special subdomain recognized by Azure. By prepending
 8. After you have created the CNAME record, return to the **Manage Custom Domain** dialog, and enter the name of your custom domain in the **Custom Domain Name** field. For example, if your domain is **contoso.com** and your subdomain is **www**, enter **www.contoso.com**; if your subdomain is **photos**, enter **photos.contoso.com**. Note that the subdomain is required.
 9. Click the checkbox that says **Advanced: Use the 'asverify' subdomain to preregister my custom domain**.
 10. Click the **Register** button to preregister your custom domain.
-    
+
     If the preregistration is successful, you will see the message **Your custom domain is active**.
 11. At this point, your custom domain has been verified by Azure, but traffic to your domain is not yet being routed to your storage account. To complete the process, return to your DNS registrar's website, and create another CNAME record that maps your subdomain to your Blob service endpoint. For example, specify the subdomain as **www** or **photos**, and the hostname as **mystorageaccount.blob.core.windows.net** (where **mystorageaccount** is the name of your storage account). With this step, the registration of your custom domain is complete.
 12. Finally, you can delete the CNAME record you created using **asverify**, as it was necessary only as an intermediary step.
@@ -104,13 +104,13 @@ For example, you might use the following URI to access a web form via a
     http://photos.contoso.com/myforms/applicationform.htm
 
 ## Unregister a custom domain from your storage account
-To unregister a custom domain, follow these steps: 
+To unregister a custom domain, follow these steps:
 
-1. Sign in to the [Azure Classic Portal](https://manage.windowsazure.com). 
-2. In the navigation pane, click **Storage**. 
-3. On the **Storage** page, click the name of the storage account to display the dashboard. 
-4. On the ribbon, click **Manage Domain**. 
-5. In the **Manage Custom Domain** dialog box, click **Unregister**. 
+1. Sign in to the [Azure Classic Portal](https://manage.windowsazure.com).
+2. In the navigation pane, click **Storage**.
+3. On the **Storage** page, click the name of the storage account to display the dashboard.
+4. On the ribbon, click **Manage Domain**.
+5. In the **Manage Custom Domain** dialog box, click **Unregister**.
 
 ## Additional Resources
 * [How to map Custom Domain to Content Delivery Network (CDN) endpoint](../cdn/cdn-map-content-to-custom-domain.md)

articles/storage/storage-dotnet-how-to-use-blobs.md

@@ -3,8 +3,8 @@ title: Get started with Azure Blob storage (object storage) using .NET | Microso
 description: Store unstructured data in the cloud with Azure Blob storage (object storage).
 services: storage
 documentationcenter: .net
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: d18a8fc8-97cb-4d37-a408-a6f8107ea8b3
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: hero-article
-ms.date: 11/17/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 ---
 
 # Get started with Azure Blob storage using .NET

articles/storage/storage-dotnet-how-to-use-tables.md

@@ -3,8 +3,8 @@ title: Get started with Azure Table storage using .NET | Microsoft Docs
 description: Store structured data in the cloud using Azure Table storage, a NoSQL data store.
 services: storage
 documentationcenter: .net
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: fe46d883-7bed-49dd-980e-5c71df36adb3
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: hero-article
-ms.date: 11/17/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 
 ---
 # Get started with Azure Table storage using .NET

articles/storage/storage-dotnet-shared-access-signature-part-1.md

@@ -3,8 +3,8 @@ title: Using Shared Access Signatures (SAS) | Microsoft Docs
 description: Learn about delegating access to Azure Storage resources, including blobs, queues, tables, and files, using shared access signatures (SAS).
 services: storage
 documentationcenter: ''
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: 46fd99d7-36b3-4283-81e3-f214b29f1152
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: article
-ms.date: 10/17/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 
 ---
 # Using Shared Access Signatures (SAS)
@@ -65,7 +65,7 @@ Version 2015-04-05 of Azure Storage introduces a new type of shared access signa
 ## How a shared access signature works
 A shared access signature is a signed URI that points to one or more storage resources and includes a token that contains a special set of query parameters. The token indicates how the resources may be accessed by the client. One of the query parameters, the signature, is constructed from the SAS parameters and signed with the account key. This signature is used by Azure Storage to authenticate the SAS.
 
-Here's an example of a SAS URI, showing the resource URI and the SAS token: 
+Here's an example of a SAS URI, showing the resource URI and the SAS token:
 
 ![sas-storage-uri][sas-storage-uri]
 
@@ -203,7 +203,7 @@ catch (StorageException e)
 When you use shared access signatures in your applications, you need to be aware of two potential risks:
 
 * If a SAS is leaked, it can be used by anyone who obtains it, which can potentially compromise your storage account.
-* If a SAS provided to a client application expires and the application is unable to retrieve a new SAS from your service, then the application's functionality may be hindered.  
+* If a SAS provided to a client application expires and the application is unable to retrieve a new SAS from your service, then the application's functionality may be hindered.
 
 The following recommendations for using shared access signatures will help balance these risks:
 
@@ -305,7 +305,7 @@ private static async Task CreateSharedAccessPolicyAsync(CloudBlobContainer conta
     // The access policy provides create, write, read, list, and delete permissions.
     SharedAccessBlobPolicy sharedPolicy = new SharedAccessBlobPolicy()
     {
-        // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request. 
+        // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request.
         // Omitting the start time for a SAS that is effective immediately helps to avoid clock skew.
         SharedAccessExpiryTime = DateTime.UtcNow.AddHours(24),
         Permissions = SharedAccessBlobPermissions.Read | SharedAccessBlobPermissions.List |
@@ -332,11 +332,11 @@ private static string GetContainerSasUri(CloudBlobContainer container, string st
     // If no stored policy is specified, create a new access policy and define its constraints.
     if (storedPolicyName == null)
     {
-        // Note that the SharedAccessBlobPolicy class is used both to define the parameters of an ad-hoc SAS, and 
-        // to construct a shared access policy that is saved to the container's shared access policies. 
+        // Note that the SharedAccessBlobPolicy class is used both to define the parameters of an ad-hoc SAS, and
+        // to construct a shared access policy that is saved to the container's shared access policies.
         SharedAccessBlobPolicy adHocPolicy = new SharedAccessBlobPolicy()
         {
-            // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request. 
+            // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request.
             // Omitting the start time for a SAS that is effective immediately helps to avoid clock skew.
             SharedAccessExpiryTime = DateTime.UtcNow.AddHours(24),
             Permissions = SharedAccessBlobPermissions.Write | SharedAccessBlobPermissions.List
@@ -379,11 +379,11 @@ private static string GetBlobSasUri(CloudBlobContainer container, string blobNam
     if (policyName == null)
     {
         // Create a new access policy and define its constraints.
-        // Note that the SharedAccessBlobPolicy class is used both to define the parameters of an ad-hoc SAS, and 
-        // to construct a shared access policy that is saved to the container's shared access policies. 
+        // Note that the SharedAccessBlobPolicy class is used both to define the parameters of an ad-hoc SAS, and
+        // to construct a shared access policy that is saved to the container's shared access policies.
         SharedAccessBlobPolicy adHocSAS = new SharedAccessBlobPolicy()
         {
-            // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request. 
+            // When the start time for the SAS is omitted, the start time is assumed to be the time when the storage service receives the request.
             // Omitting the start time for a SAS that is effective immediately helps to avoid clock skew.
             SharedAccessExpiryTime = DateTime.UtcNow.AddHours(24),
             Permissions = SharedAccessBlobPermissions.Read | SharedAccessBlobPermissions.Write | SharedAccessBlobPermissions.Create

articles/storage/storage-dotnet-shared-access-signature-part-2.md

@@ -3,8 +3,8 @@ title: Create and use a SAS with Blob storage | Microsoft Docs
 description: This tutorial shows you how to create shared access signatures for use with Blob storage, and how to consume them from your client applications.
 services: storage
 documentationcenter: ''
-author: tamram
-manager: carmonm
+author: mmacy
+manager: timlt
 editor: tysonn
 
 ms.assetid: 491e0b3c-76d4-4149-9a80-bbbd683b1f3e
@@ -13,8 +13,8 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: article
-ms.date: 10/18/2016
-ms.author: tamram
+ms.date: 12/08/2016
+ms.author: marsma
 
 ---
 # Shared Access Signatures, Part 2: Create and use a SAS with Blob storage
@@ -40,7 +40,7 @@ In Visual Studio, create a new Windows console application and name it **Generat
 At the top of the Program.cs file, add the following **using** statements:
 
 ```csharp
-using System.IO;    
+using System.IO;
 using Microsoft.WindowsAzure;
 using Microsoft.WindowsAzure.Storage;
 using Microsoft.WindowsAzure.Storage.Blob;
@@ -112,7 +112,7 @@ Console.WriteLine("Container SAS URI: " + GetContainerSasUri(container));
 Console.WriteLine();
 ```
 
-Compile and run to output the shared access signature URI for the new container. The URI will be similar to the following URI:       
+Compile and run to output the shared access signature URI for the new container. The URI will be similar to the following URI:
 
 `https://storageaccount.blob.core.windows.net/sascontainer?sv=2012-02-12&se=2013-04-13T00%3A12%3A08Z&sr=c&sp=wl&sig=t%2BbzU9%2B7ry4okULN9S0wst%2F8MCUhTjrHyV9rDNLSe8g%3D`
 
@@ -155,7 +155,7 @@ static string GetBlobSasUri(CloudBlobContainer container)
 }
 ```
 
-At the bottom of the **Main()** method, add the following lines to call **GetBlobSasUri()**, before the call to **Console.ReadLine()**, and write the shared access signature URI to the console window:    
+At the bottom of the **Main()** method, add the following lines to call **GetBlobSasUri()**, before the call to **Console.ReadLine()**, and write the shared access signature URI to the console window:
 
 ```csharp
 //Generate a SAS URI for a blob within the container, without a stored access policy.
@@ -198,7 +198,7 @@ static void CreateSharedAccessPolicy(CloudBlobClient blobClient, CloudBlobContai
 }
 ```
 
-At the bottom of the **Main()** method, before the call to **Console.ReadLine()**, add the following lines to first clear any existing access policies and then call the **CreateSharedAccessPolicy()** method:    
+At the bottom of the **Main()** method, before the call to **Console.ReadLine()**, add the following lines to first clear any existing access policies and then call the **CreateSharedAccessPolicy()** method:
 
 ```csharp
 //Clear any existing access policies on container.
@@ -269,7 +269,7 @@ static string GetBlobSasUriWithPolicy(CloudBlobContainer container, string polic
 }
 ```
 
-At the bottom of the **Main()** method, before the call to **Console.ReadLine()**, add the following lines to call the **GetBlobSasUriWithPolicy** method:    
+At the bottom of the **Main()** method, before the call to **Console.ReadLine()**, add the following lines to call the **GetBlobSasUriWithPolicy** method:
 
 ```csharp
 //Generate a SAS URI for a blob within the container, using a stored access policy to set constraints on the SAS.
@@ -331,8 +331,8 @@ To test the shared access signatures created in the previous examples, we'll cre
 
 > [!NOTE]
 > If more than 24 hours have passed since you completed the first part of the tutorial, the signatures you generated will no longer be valid. In this case, you should run the code in the first console application to generate fresh shared access signatures for use in the second part of the tutorial.
-> 
-> 
+>
+>
 
 In Visual Studio, create a new Windows console application and name it **ConsumeSharedAccessSignatures**. Add references to **Microsoft.WindowsAzure.Configuration.dll** and **Microsoft.WindowsAzure.Storage.dll**, as you did previously.
 
@@ -445,7 +445,7 @@ static void UseContainerSAS(string sas)
         Console.WriteLine("Delete operation failed for SAS " + sas);
         Console.WriteLine("Additional error information: " + e.Message);
         Console.WriteLine();
-    }        
+    }
 }
 ```
 
@@ -540,7 +540,7 @@ static void UseBlobSAS(string sas)
         Console.WriteLine("Delete operation failed for SAS " + sas);
         Console.WriteLine("Additional error information: " + e.Message);
         Console.WriteLine();
-    }        
+    }
 }
 ```