title: The request could not be completed (Not Found)
body: <p>I have added a vanilla mobile service, selecting the defaults all the way. It is a .Net backend, using a new 20MB DB on an existing server I use in the North Europe DC. I created a blank Windows Store App, added the MobileServices nuget package and then followed the instructions to connect my MobileService to my app by adding the MobileServicesClient to my App.xaml class.  Then I added a button with an event handler. The handler calls an async function to insert a TodoItem object into the database.</p>
  
  <p>App.xaml.cs</p>
  
  <pre><code>public static MobileServiceClient MobileService = new MobileServiceClient(
               "https://???.azure-mobile.net/",
               "???");
  </code></pre>
  
  <p>I have replaced the URI and Token with ???. The one I used came from my Azure Portal for this Mobile Service.</p>
  
  <p>MainPage.xaml.cs</p>
  
  <pre><code>private void Button_Click(object sender, RoutedEventArgs e)
  {
      CreateItem();
  }
  
  private async  void CreateItem()
  {
      TodoItem item = new TodoItem { Text = "Sort This", Complete = false };
      try
      {
          await App.MobileService.GetTable&lt;TodoItem&gt;().InsertAsync(item);
      }
      catch(MobileServiceInvalidOperationException ex1)
      {
          Debug.WriteLine(ex1.Message);
      }
      catch(Exception ex)
      {
          Debug.WriteLine(ex.Message);
      }
  }
  </code></pre>
  
  <p>When I run this code and click the button a MobileServiceInvalidOperationException is raised:</p>
  
  <p>"{"The request could not be completed.  (Not Found)"}"</p>
  
  <p>I am using VS2013, with Service Pack 2 installed and WindowsAzure.MobileServices 1.2.3.</p>
  
  <p>The MobileService is running as I can navigate to <a href="https://MyMobileService.azure-mobile.net/" rel="nofollow">https://MyMobileService.azure-mobile.net/</a> but, if I click Check It Out, I am asked to Authenticate (MyMobileService is not the actual Uri).</p>
  
  <p>The post request looks ok, but the response is a 404.</p>
  
  <p>I have been working on this all day, including using Windows Phone, with no luck...</p>
  
  <p>I know I must be doing something wrong, or there is an issue with Azure in Northern Europe, but I can't sort it out.</p>
  
  <p>Any help much appreciated.</p>
  
  <p>Jason.</p>