Merge pull request #452 from mollybostic/weekly_1009

Merging weekly content into Master branch.

DevCenter/Java/HowTo/service-bus-queues.md

@@ -20,87 +20,7 @@ messages**, and **deleting queues**.
 -   [How to: Handle Application Crashes and Unreadable Messages][]
 -   [Next Steps][]
 
-## <a name="bkmk_WhatAreSvcBusQueues"> </a>What are Service Bus Queues?
-
-Service Bus Queues support a **brokered messaging communication** model.
-When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.
-
-![Service Bus Queue Diagram][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
--   Communication between web and worker roles in a multi-tier Windows
-    Azure application
--   Communication between on-premises apps and Windows Azure hosted apps
-    in a hybrid solution
--   Communication between components of a distributed application
-    running on-premises in different organizations or departments of an
-    organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1.  Log on to the [Windows Azure Management Portal][].
-2.  In the lower left navigation pane of the Management Portal, click
-    **Service Bus, Access Control & Caching**.
-3.  In the upper left pane of the Management Portal, click the **Service
-    Bus** node, and then click the **New** button.  
-    ![Service Bus Node screenshot][]
-4.  In the **Create a new Service Namespace** dialog, enter a
-    **Namespace**, and then to make sure that it is unique, click the
-    **Check Availability** button.  
-    ![Create a New Namespace screenshot][]
-5.  After making sure the namespace name is available, choose the
-    country or region in which your namespace should be hosted (make
-    sure you use the same country/region in which you are deploying your
-    compute resources), and then click the **Create Namespace** button.
-    Having a compute instance is optional, and the service bus can be
-    consumed from any application with internet access.  
-
-     The namespace you created will then appear in the Management Portal
-    and takes a moment to activate. Wait until the status is **Active**
-    before moving on.
-
-## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1.  In the left navigation pane, click the **Service Bus** node, to
-    display the list of available namespaces:   
-    ![Available Namespaces screenshot][]
-2.  Select the namespace you just created from the list shown:   
-    ![Namespace List screenshot][]
-3.  The right-hand **Properties** pane will list the properties for the
-    new namespace:   
-    ![Properties Pane screenshot][]
-4.  The **Default Key** is hidden. Click the **View** button to display
-    the security credentials:   
-    ![Default Key screenshot][]
-5.  Make a note of the **Default Issuer** and the **Default Key** as you
-    will use this information below to perform operations with the
-    namespace.
+<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
 
 ## <a name="bkmk_ConfigApp"> </a>Configure Your Application to Use Service Bus
 
@@ -320,9 +240,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
 topic [Queues, Topics, and Subscriptions][] for more information.
 
   [Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
-  [What are Service Bus Queues?]: #bkmk_WhatAreSvcBusQueues
-  [Create a Service Namespace]: #bkmk_CreateSvcNamespace
-  [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
+  [What are Service Bus Queues?]: #what-are-service-bus-queues
+  [Create a Service Namespace]: #create-a-service-namespace
+  [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
   [Configure Your Application to Use Service Bus]: #bkmk_ConfigApp
   [How to: Create a Security Token Provider]: #bkmk_HowToCreateQueue
   [How to: Send Messages to a Queue]: #bkmk_HowToSendMsgs

DevCenter/Java/HowTo/service-bus-topics.md

@@ -22,81 +22,7 @@ messages to a topic**, **receiving messages from a subscription**, and
 -   [How to: Delete Topics and Subscriptions][]
 -   [Next Steps][]
 
-## <a name="bkmk_WhatAreSvcBusTopics"> </a>What are Service Bus Topics and Subscriptions?
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.  
-![Service Bus Topics diagram][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages to a topic are received by which topic
-subscriptions.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
-
-To begin using Service Bus topics in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-**To create a service namespace:**
-
-1.  Log on to the [Windows Azure Management Portal][].
-2.  In the lower left navigation pane of the Management Portal, click
-    **Service Bus, Access Control & Caching**.
-3.  In the upper left pane of the Management Portal, click the **Service
-    Bus** node, and then click the **New** button.   
-    ![Service Bus Node screenshot][]
-4.  In the **Create a new Service Namespace** dialog, enter a
-    **Namespace**, and then to make sure that it is unique, click the
-    **Check Availability** button.   
-    ![Create a New Namespace ][]
-5.  After making sure the namespace name is available, choose the
-    country or region in which your namespace should be hosted (make
-    sure you use the same country/region in which you are deploying your
-    compute resources), and then click the **Create Namespace** button.
-    Having a compute instance is optional, and the service bus can be
-    consumed from any application with internet access.  
-
-     The namespace you created will then appear in the Management Portal
-    and takes a moment to activate. Wait until the status is **Active**
-    before moving on.
-
-## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a topic, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1.  In the left navigation pane, click the **Service Bus** node, to
-    display the list of available namespaces:   
-    ![Available Namespaces ][Service Bus Node screenshot]
-2.  Select the namespace you just created from the list shown:  
-    ![Namespace List screenshot][]
-3.  The right-hand **Properties** pane will list the properties for the
-    new namespace:   
-    ![Properties Pane screenshot][]
-4.  The **Default Key** is hidden. Click the **View** button to display
-    the security credentials:   
-    ![Default Key screenshot][]
-5.  Make a note of the **Default Issuer** and the **Default Key** as you
-    will use this information below to perform operations with the
-    namespace.
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
 
 ## <a name="bkmk_ConfigYourApp"> </a>Configure Your Application to Use Service Bus
 
@@ -409,9 +335,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
 topic [Queues, Topics, and Subscriptions][] for more information.
 
   [Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
-  [What are Service Bus Topics and Subscriptions?]: #bkmk_WhatAreSvcBusTopics
-  [Create a Service Namespace]: #bkmk_CreateSvcNamespace
-  [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
+  [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
+  [Create a Service Namespace]: #create-a-service-namespace
+  [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
   [Configure Your Application to Use Service Bus]: #bkmk_ConfigYourApp
   [How to: Create a Topic]: #bkmk_HowToCreateTopic
   [How to: Create Subscriptions]: #bkmk_HowToCreateSubscrip

DevCenter/Mobile/HowTo/mobile-microsoft-account-auth-steps.md

@@ -0,0 +1,37 @@
+<div class="dev-callout"><b>Note</b>
+<p>When you intend to also provide single sign-on or push notifications from a Windows Store app, consider also registering your app with the Windows Store. For more information, see <a href="/en-us/develop/mobile/howto/register-for-live-connect-auth">Register your Windows Store apps for Windows Live Connect authentication</a>.</p>
+</div>
+
+1. Navigate to the [My Applications] page in the Live Connect Developer Center, and log on with your Microsoft account, if required. 
+
+2. Click **Create application**, then type an **Application name** and click **I accept**.
+
+   ![][1] 
+
+   This registers the application with Live Connect.
+
+10. Make a note of the value of **Client ID** and **Client secret**. 
+
+   ![][2]
+
+    <div class="dev-callout"><b>Security Note</b>
+	<p>The client secret is an important security credential. Do not share the client secret with anyone or distribute it with your app.</p>
+    </div>
+
+<!-- Anchors. -->
+
+<!-- Images. -->
+[1]: ../Media/mobile-services-live-connect-add-app.png
+[2]: ../Media/mobile-services-live-connect-app-details.png
+
+<!-- URLs. -->
+[Single sign-on for Windows Store apps by using Live Connect]: ./mobile-services-single-sign-on-win8-dotnet.md
+[Submit an app page]: http://go.microsoft.com/fwlink/p/?LinkID=266582
+[My Applications]: http://go.microsoft.com/fwlink/p/?LinkId=262039
+[Get started with Mobile Services]: ./mobile-services-get-started.md
+[Get started with authentication]: ./mobile-services-get-started-with-users-dotnet.md
+[Get started with push notifications]: ./mobile-services-get-started-with-push-dotnet.md
+[Authorize users with scripts]: ./mobile-services-authorize-users-dotnet.md
+[JavaScript and HTML]: ./mobile-services-get-started-with-users-js.md
+[WindowsAzure.com]: http://www.windowsazure.com/
+[Windows Azure Management Portal]: https://manage.windowsazure.com/

DevCenter/Mobile/Chunks/mobile-facebook-auth-steps.md → DevCenter/Mobile/HowTo/mobile-services-register-facebook-auth.md

@@ -4,13 +4,13 @@
 
 # Register your apps for Facebook authentication with Mobile Services
 
-This topic shows you how to register your apps to be able to use Facebook as an authentication provider Windows Azure Mobile Services. 
+This topic shows you how to register your apps to be able to use Facebook to authenticate with Windows Azure Mobile Services. 
 
 <div class="dev-callout"><b>Note</b>
-<p>To complete the procedure in this topic, you must have a Facebook account that has a verified email address and a mobile phone number. To create a new Facebook account, go to facebook.com.</p>
+<p>To complete the procedure in this topic, you must have a Facebook account that has a verified email address and a mobile phone number. To create a new Facebook account, go to <a href="http://go.microsoft.com/fwlink/p/?LinkId=268285" target="_blank">facebook.com</a>.</p>
 </div> 
 
-1. Navigate to [Facebook Developers] web site and sign-in with your Facebook account credentials.
+1. Navigate to the <a href="http://go.microsoft.com/fwlink/p/?LinkId=268286" target="_blank">Facebook Developers</a> web site and sign-in with your Facebook account credentials.
 
 2. (Optional) If you have not already registered, click **Register Now** button, accept the policy, provide any and then click **Done**. 
 
@@ -20,8 +20,6 @@ This topic shows you how to register your apps to be able to use Facebook as an
 
    ![][1]
 
-   This displays the 
-
 4. Choose a unique name for your app, select **OK**.
 
    ![][2]
@@ -32,15 +30,15 @@ This topic shows you how to register your apps to be able to use Facebook as an
 
    ![][3]
 
-6. Make a note of the value of **App ID** and **App Secret**. 
+6. Make a note of the values of **App ID** and **App Secret**. 
 
    ![][4]
 
     <div class="dev-callout"><b>Security Note</b>
 	<p>The app secret is an important security credential. Do not share this secret with anyone or distribute it with your app.</p>
     </div>
 
-You are now ready to integrate authentication by using Facebook into your app by providing the App ID and App Secret values to Mobile Services.
+You are now ready to use a Facebook login for authentication in your app by providing the App ID and App Secret values to Mobile Services. 
 
 <!-- Anchors. -->
 
@@ -52,7 +50,8 @@ You are now ready to integrate authentication by using Facebook into your app by
 [4]: ../Media/mobile-services-facebook-completed.png
 
 <!-- URLs. -->
-[Facebook Developers]: http://developer.facebook.com
+[facebook.com]: http://go.microsoft.com/fwlink/p/?LinkId=268285
+[Facebook Developers]: http://go.microsoft.com/fwlink/p/?LinkId=268286
 [Get started with authentication]: ./mobile-services-get-started-with-users-dotnet.md
 [WindowsAzure.com]: http://www.windowsazure.com/
 [Windows Azure Management Portal]: https://manage.windowsazure.com/