Deallocating a Web/Worker Roles Cloud Service

I'm seeking some clarification on whether its possible to shutdown a PaaS Cloud Service into a non-chargeable state in the same way one can do this with IaaS virtual machine deployments? In an automated CI/CD environment then PaaS is attractive but paying
for instances we use for development to run the 16-18 hours a day no one is using them isn't. Yet shutting down at night and restarting IaaS VMs in the morning via scheduled automated tasks appears fairly trivial to achieve. 
Shutting down PaaS instances via Powershell or the Management API fails, stopping the service via the portal appears to still leave them chargeable.  So the only solution currently appears to be fully delete them and then recreate when you need
them again (along with the time penalties spinning up new instances carries). Am I missing something or is this really not possible? If it isn't possible then is it something that is in the pipeline? (I had heard on the grapevine that the PaaS solution that
currently exists is pencilled in to be replaced/removed).

Hi,
Worker and Web Roles are charged per hour of deployment so even if doing nothing it is being charged out as you have physically commission the vm to be spun up. Even if the role is stopped but the deployment hasn't been deleted you will still pay for the
instance. So, it is not possible now, At currently, please vote this voice:
http://feedback.azure.com/forums/34192--general-feedback/suggestions/6887568-not-bill-for-a-stopped-cloud-service
Best Regards,
Jambor 
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

  • Web worker on cloud service - some questions

    Hi all;
    Ok, I'm trying to get a web worker implemented (following this) working off of a message queue and have a couple of questions:
    So I get a message, perform my operation on it (in my case an update to Sql Azure), and then delete the message. What if Azure shuts me down after I complete the update but before the message is deleted. Then when I start up again, won't I be processing
    that message again?
    If I mark the message as processing, and then Azure shuts me down just before I call update, then won't I lose that operation?
    It says sleep for 1 minute if there's no messages. Is there a way to instead block on an event and trigger that event when I add another message?
    thanks - dave
    What we did for the last 6 months -
    Made the world's coolest reporting & docgen system even more amazing

    Hello,
    First, azure cloud service has a high availability and it rarely shut down. If the worker role app shuts down, also you unnecessary worry about the azure storage queue service. As this
    article mentioned, "Your code de-queues a message from a queue in two steps. When you call
    GetMessage, you get the next message in a queue. A message returned from
    GetMessage becomes invisible to any other code reading messages from this queue. By default, this message stays invisible for 30 seconds. To finish removing the message from the queue, you must also call
    DeleteMessage. This two-step process of removing a message assures that
    if your code fails to process a message due to hardware or software failure, another instance of your code can get the same message and try again. Your code calls
    DeleteMessage right after the message has been processed."  So we should call the DeleteMessage method after completed your operating.  
    As for your third question, not really there is a trigger for worker role app. We should use a long running process to read messages from storage queue.
    while (true)
    try
    //your code to read queue messages
    //you can make the thread sleep some times
    System.Threading.Thread.Sleep(1000 * 60);
    catch (Exception ex)
    System.Threading.Thread.Sleep(1000 * 60);
    Best Regards,
    Fuxiang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a
    href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

  • Can my hp color laserjet 3500 work with cloud services

    can my hp color laserjet 3500 work with cloud services
    This question was solved.
    View Solution.

    The printer listed doesn't support cloud services.
    Cloud Services supported printers

  • Visual Studio cannot remote debug Azure cloud service: There was a failure to launch the remote debugger

    I am trying to invoke remote debugger on an Azure worker role cloud service, following the example of
    http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
    But on attaching the remote debugger for the cloud service instance
    Microsoft Visual Studio
    There was a failure to launch the remote debugger.
    OK  
    According to somebody else's extra coverage on the topic, there are extra ports 4016/4017 that need to be taken care of (but do they have to be exposed externally)?
    http://developers.de/blogs/damir_dobric/archive/2014/02/04/behind-windows-azure-remote-debugger.aspx
    So servicedefinition.csdef gets
        <Endpoints>
          <InputEndpoint name="Endpoint1" protocol="http" port="80" />
          <InputEndpoint name="RemoteDebugger" protocol="tcp" port="4016" localPort="4016" />
          <InputEndpoint name="RemoteDebugger2" protocol="tcp" port="4017" localPort="4017" />
          <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
            <AllocatePublicPortFrom>
              <FixedPortRange min="30400" max="30424" />
            </AllocatePublicPortFrom>
          </InstanceInputEndpoint>
          <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
            <AllocatePublicPortFrom>
              <FixedPortRange min="31400" max="31424" />
            </AllocatePublicPortFrom>
          </InstanceInputEndpoint>
        </Endpoints>
    Serviceconfiguration.cscfg gets
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.3" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="THUMBNAIL" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="THUMBNAIL" />
        </ConfigurationSettings>
        <Certificates>
          <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="THUMBNAIL" thumbprintAlgorithm="sha1"
    />
        </Certificates>
    But all these are to no avail; the same error still pops for Visual Studio 2013 Update 4; Azure SDK 2.3
    Anybody regularly perform remote debugging for Azure cloud services?
    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

    And, how do I control that in Visual Studio?
    All I get is the Attach Debugger... context menu option in the Azure cloud service nodes in Server Explorer. That is where it is failing. There are no customisable options.
    Because of that, the Attach to Process dialog box is unable to retrieve the list of processes (to debug) in the remote worker role instance server.
    I tested a blank-template worker role project and published to a new cloud project, and this simplistic copy had no problems with the Remote debugger.
    Now the question is, what is it about this real-world project/cloud service that is different from blank sample? From what I compare between what I think are the relevant settings, there are none.
    ServiceDefinition.csdef
    <Imports>
    <Import moduleName="Diagnostics" />
    <Import moduleName="RemoteAccess" />
    <Import moduleName="RemoteForwarder" />
    <Import moduleName="RemoteDebuggerConnector" />
    </Imports>
    <Contents>
    <Content destination=".\">
    <SourceDirectory path="D:\Projects\experiments\workerrole1\workerrole1\rcf\Debug\RemoteDebuggerContent\" />
    </Content>
    </Contents>
    <Endpoints>
    <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
    <AllocatePublicPortFrom>
    <FixedPortRange min="30400" max="30424" />
    </AllocatePublicPortFrom>
    </InstanceInputEndpoint>
    <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
    <AllocatePublicPortFrom>
    <FixedPortRange min="31400" max="31424" />
    </AllocatePublicPortFrom>
    </InstanceInputEndpoint>
    </Endpoints>
    ServiceConfiguration.cscfg
    <ConfigurationSettings>
    <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=storage;AccountKey=" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2015-12-31T23:59:59.0000000+08:00" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.4" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="" />
    </ConfigurationSettings>
    <Certificates>
    <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="" thumbprintAlgorithm="sha1" />
    <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="" thumbprintAlgorithm="sha1" />
    </Certificates>
    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

  • How do I tell my clients to configure the connectionstrings for a cloud service?

    I have an application that exists in two forms
    A Windows Service
    A Clouse Service with a Web Worker Role
    Both applications have an encrypted connection string in the app.config;
    for clients using the Windows Service I know how to tell them to change the config file.
    For a cloud service is it possible to edit the configuration file?
    I read something about Azure Settings, but I can't find any good information about that, is that the preferred method for setting environment settings in a Cloud Service?
    Can you remote in to a VM or whatever hosts the Cloud Service?
    Thank you for any help. I am writing the documentation about how to setup the Azure environment and I realized I don't know myself, I only know how to publish with Visual Studio to a cloud service with the values already set. That works, but I can't
    tell a client to use Visual Studio.

    Hi,
    For a cloud service, though it is possible to access instance VMs and do changes on their file system by RDP sessions, but it is not recommended, as you will end up loosing your changes if role instance VMs are restarted.
    If you really want to keep certain settings configurable and which will be shared by all your role instances, best way to do is to utilise the cloud service configurations, typically you mention these settings in .cscfg file and you can also edit those using
    azure management portal.
    You can also access those from your code 
    string settingValue = CloudConfigurationManager.GetSetting("SettingString");
    Read more about it here - http://msdn.microsoft.com/en-us/library/azure/ee405486.aspx
    http://haishibai.blogspot.in/2012/09/windows-azure-cloud-service.html
    Bhushan | Blog |
    LinkedIn | Twitter

  • "Failed to debug the Windows Azure Cloud Service project. The Output directory .... does not exist" - Looking for Solution Config Name Folder?

    Good evening,
    I've been working on and with a VS2013 Update 2 / Azure SDK 2.3 Cloud Service project for a while now and never had a problem debugging it (setting the .ccproj Project as Startup Project) but at the moment I cannot Debug it anymore - I always get the following
    error message:
    Failed to debug the Windows Azure Cloud Service project.  The output directory 'D:\Workspace\Development\Sources\AzureBackend\csx\Backend - Debug' does not exist.
    Now what's odd here, is the last part - the "Backend - Debug" is the Solution configuration name, ALL projects in that particular solution configuration are set to the Debug Configuration. The .ccproj file also only specifies Debug|Any CPU (and
    Release|Any CPU respectively) as its output folder(s). Why is the Solution config appearing up there?
    And more importantly.. why is this happening and what can I do?!
    Thanks,
    -Jörg
    Ps: there seems to be a related
    connect bug and these sorts of issues do appear around the forums but none contains a solution (neither reinstalling the Azure SDK nor cloaking the workspace/re-retrieving & building everything worked).

    Good morning Jambor,
    I already tried de-installing everything Azure-Tooling related including the Azure SDK, Restarting my machine and re-installing the SDK.
    Same result. I can build the .ccproj perfectly fine and the cspack file IS generated perfectly fine, only debugging does not work and there's NO information in the VS output window (again - all projects succeed to build).
    I tried explicitely running VS as Administrator, no change. I removed all IIS Express sites (as the ccproj has one web worker role), remapped my local TFS workspace.. nothing helped.
    As building works, deploying to Azure Cloud Service (manually and via Publish inside VS) all works -perfectly-, I am pretty sure this IS a bug and I'd LOVE to help to get this fixed. As I said, currently I cannot debug and/or run & test my work, hence
    I cannot do ANY work.

  • Cloud Services

    Hi,
    If I'm right (and read correctly earlier posts) Web Role(s) and Worker Role(s) in a Cloud Service can only be created in a Visual Studio project? What about a SQL Server (e.g. Web Edition) database in a Cloud Service? Can this also be created in Visual Studio?
    I suppose there's a difference between the Windows Azure SQL Database and the Windows Azure Cloud Service SQL Database?
    One additional question: besides that a Cloud Service (web/worker role) are managed (PAAS), I suppose I can use for a "worker role" and "web role" also a virtual machine, and for a "web role" eventually also a web application:
    in which case is it best to select which of the options?
    Thanks.

    Hi,
    >>Web Role(s) and Worker Role(s) in a Cloud Service can only be created in a Visual Studio project?
    We can use visual studio to create web role or worker role only click a few times, but visual studio is not the only way to create web role or worker role, we also can use command line to do this. see more at:
    http://www.windowsazure.com/en-us/documentation/articles/cloud-services-php-create-web-role/#AddRole
    >>What about a SQL Server (e.g. Web Edition) database in a Cloud Service? Can this also be created in Visual Studio?
    Base on your description, Windows Azure Cloud Service SQL Database may be the sql database on-premise, refer to
    http://stackoverflow.com/questions/3235164/what-is-the-difference-between-sql-azure-and-sql-server-2008 for more information about the difference, we can create azure table via visual studio, refer to
    http://stackoverflow.com/questions/15604413/gui-for-creating-azure-database-tables for more details.
    When we deploy one application to azure cloud service, we can see all instances in azure manage portal in cloud service "INSTANCE" tab, each instance was a vm, if we do some special things (such as configure IIS install server) we can choose
    azure vm, if we use cloud service instance, all your configure may be lose after restart.
    Best Regards
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Running mail server on Worker Role

    I'm trying to use a Worker role to setup an SMTP server.  I used Visual Studio to provision the worker role, assigned a ReservedIP address to it, setup ReverseDNS, and specified an inputendpoint for SMTP on port 25.  
    Question, when you specify an InputEndpoint, does it poke a hole in the firewall of the VM? Or does it assign that to the WorkerRole application?  I wanted to use a Web Service instead of a regular VM to install an SMTP server, but I'm not having any
    luck.  I installed SmarterMail on the Worker Role service and cannot get port 25 to respond for Smartermail.  It sends mail just fine, but is blocked for inbound SMTP.
    Any ideas?
    Jim Braun

    Hi,
     Thanks for Posting.
     Yes, Input Endpoints enable External Traffic to be load balanced to your Web/Worker Role VM  through the Firewall.
     You might want to check this thread for additional information :
    https://social.msdn.microsoft.com/Forums/en-US/1e284bf7-2f9d-44ca-b5f8-f29a8654633a/receive-email-using-worker-role?forum=windowsazuredevelopment
     Also refer to this Link which talks about setting up SMTP on worker role :
    http://blog.smarx.com/posts/emailtheinternet-com-sending-and-receiving-email-in-windows-azure
    Regards,
    Nithin.Rathnakar

  • How is a Worker Role hosted?

    Hi
    How is a worker role hosted in Azure. What process is it in?
    I'm thinking of how to test locally or an on premise version. Is the Azure host process simply a windows service?
    I'm writing a solution that uses the Service Bus for Window Server 1.1 as my customers all use on-premise servers (at the moment). It would be handy if I could create a worker role for on premise solutions :)
    Thanks
    Graham

    Hi Graham,
    Thanks for your posting!
    Base on my understanding, Azure worker role is used for some services would run in the background to collect, transform, and prepare data.  In other words, Azure work role could
    executive function to a background processor .
    In worker role project, we could see  the file named "WorkerRole.cs". The class inherited the "RoleEntryPoint".
    public class WorkerRole : RoleEntryPoint
    public override void Run()
    // This is a sample worker implementation. Replace with your logic.
    Trace.TraceInformation("WorkerRole1 entry point called");
    while (true)
    Thread.Sleep(10000);
    Trace.TraceInformation("Working");
    public override bool OnStart()
    // Set the maximum number of concurrent connections
    ServicePointManager.DefaultConnectionLimit = 12;
    // For information on handling configuration changes
    // see the MSDN topic at http://go.microsoft.com/fwlink/?LinkId=166357.
    return base.OnStart();
    When one worker role instance was starting, it could be executed "OnStart()" method firstly. Then in a worker role’s lifecycle is the "Run" method, typically implemented as an infinite loop, such as "While(true) ".
    In fact, if the Run method terminated, the instance would be restarted or recycled again. Please see this video (http://channel9.msdn.com/Series/Windows-Azure-Cloud-Services-Tutorials/Introduction-to-Windows-Azure-Worker-Roles-Part-1).
    For your question----" Is the Azure host process simply a windows service?", the answer is that one worker role can be one or more than one instance (VM).
    And in your scenarios, Worker role could meet your requirement. In VS, Azure SDK support one project template named "Worker role with service bus queue". Please see this documents:
    http://msdn.microsoft.com/en-us/library/azure/jj149831.aspx
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • What are Azure limitations for Websockets in Cloud Services (web and worker role)?

    A WebSocket Server should be built on Azure platform with OnPrem connections and have questions regarding limitations for Websockets in Azure Cloud Services - web and worker roles.
    Websockets can be configured for Web Sites and limitations are understood, but Azure Websites is not an option. 
    Nevertheless it is planned to run a web service (without UI - no web site) as a Cloud service which has secure websocket (WSS) connections to OnPrem machines. Websocket protocol is enabled for IIS8 on Cloud services web and worker roles. Azure Service Bus Relay
    is not an option.
    Questions:
    1) Are Websockets supported for Azure Cloud services web and worker roles? we assume yes
    2) What are potential limitations from Azure side to support concurrent Websocket connections? We are aware that CPU, memory etc are limitations, but are there additional limitations from MS Azure side? 
     

    Hi,
    As I know, azure cloud service web and worker role support Websockets, users can connect to the role via the special endpoint, if we use Azure cloud service, I think we can monitor the metrics such as CPU, memory, etc... and scale our cloud service via these
    metrics to keep the websockets working, refer to
    http://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-scale/ for more information about how to scale a cloud service.
    Regards

  • Is this the best design for asynchronous notifications (such as email)? Current design uses Web Site, Azure Service Bus Queue, Table Storage and Cloud Service Worker Role.

    I am asking for feedback on this design. Here is an example user story:
    As a group admin on the website I want to be notified when a user in my group uploads a file to the group.
    Easiest solution would be that in the code handling the upload, we just directly create an email message in there and send it. However, this seems like it isn't really the appropriate level of separation of concerns, so instead we are thinking to have a separate
    worker process which does nothing but send notifications. So, the website in the upload code handles receiving the file, extracting some metadata from it (like filename) and writing this to the database. As soon as it is done handling the file upload it then
    does two things: Writes the details of the notification to be sent (such as subject, filename, etc...) to a dedicated "notification" table and also creates a message in a queue which the notification sending worker process monitors. The entire sequence
    is shown in the diagram below.
    My questions are: Do you see any drawbacks in this design? Is there a better design? The team wants to use Azure Worker Roles, Queues and Table storage. Is it the right call to use these components or is this design unnecessarily complex? Quality attribute
    requirements are that it is easy to code, easy to maintain, easy to debug at runtime, auditable (history is available of when notifications were sent, etc...), monitor-able. Any other quality attributes you think we should be designing for?
    More info:
    We are creating a cloud application (in Azure) in which there are at least 2 components. The first is the "source" component (for example a UI / website) in which some action happens or some condition is met that triggers a second component or "worker"
    to perform some job. These jobs have details or metadata associated with them which we plan to store in Azure Table Storage. Here is the pattern we are considering:
    Steps:
    Condition for job met.
    Source writes job details to table.
    Source puts job in queue.
    Asynchronously:
    Worker accepts job from queue.
    Worker Records DateTimeStarted in table.
    Queue marks job marked as "in progress".
    Worker performs job.
    Worker updates table with details (including DateTimeCompleted).
    Worker reports completion to queue.
    Job deleted from queue.
    Please comment and let me know if I have this right, or if there is some better pattern. For example sake, consider the work to be "sending a notification" such as an email whose template fields are filled from the "details" mentioned in
    the pattern.

    Hi,
    Thanks for your posting.
    This development mode can exclude some errors, such as the file upload complete at the same time... from my experience, this is a good choice to achieve the goal.
    Best Regards,
    Jambor  
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Is it possible to do Continuous deployment for azure cloud services(website,web and worker roles) using VSO Release management?

    Hi,
    I am trying to do continuous deployment using visual studio online and release management for Azure cloud services. But not able to find the way to do it(with the help of different blogs, those are describing using VM only).
    I tried using Release management visual studio extension also. But no Luck.
    Please help me if it is possible to do continuous deployment using release management.
    Thanks,
    Phani

    Hi,
     Please refer to the following Forum Thread with similar question which has been answered. Let us know if this helps.
     https://social.msdn.microsoft.com/Forums/en-US/9d8322f6-36e5-4cca-a982-d420d34d2072/realease-management-deployment-to-azure-websites-webworker-roles?forum=tfsbuild
    Regards,
    Nithin Rathnakar

  • How to develop and deploy multiple worker roles in single azure cloud services?

    I am Manikandan, From Myeasydocs.com.
    We have developed our application as web projects.  Now we are going to move to azure cloud services, i have successfully migrated our application in cloud services and it worked fine. I am having difficulties with back ground task. i have nearly 12
    schedule tasks in our applications. I need assist on creating multiple worker role creation and deployment.
    Is there is any site on explaining the worker role process in details?
    Thanks in advance .. !!

    Hi,
    In Worker role, Applications hosted within worker roles can run asynchronous, long-running or perpetual tasks independent of user interaction or input. It is a service component that is useful for generalized development, and may perform background processing
    for a web role. A worker role is frequently used for long-running tasks that are non-interactive, but you can host any type of workload.
    I suggest you to follow the below article which explains about Creating and Deploying of Web Roles and Worker Roles in Azure Cloud Service using Visual Studio.
    https://msdn.microsoft.com/en-us/magazine/jj618299.aspx
    Hope this helps !
    Regards,
    Sowmya

  • Cloud service web role did not get request

    Hi Team,
    we have an application host in web role in a cloud service, 
    sometimes it keeps loading when clicking a button in GUI and got no response till our GUI timeout (30 minutes)
    we use Fiddler to trace the http request and also check IIS logs and found that sometimes the web role didn't get a request,  sometimes the IIS
    got the request and finished to processe the request but didn't return result to GUI.
    it seems the message lost during interaction between UI and web role.
    note that this problems comes out just recently.
    is there some known issues related with this kind of problems. 
    thanks in advance.

    hi Baker,
    Firstly, I need confirm what's meaning is GUI from your description ? The GUI is your cloud service project UI? Or your UI in your client?
    Secondly, base on my experience, we usually could occur timeout error because of the azure load balancer and the long time request.
    For this error, I recommend you refer to those thread:
    Azure Web Role - Long Running Request (Load Balancer Timeout?)
    Windows Azure Load Balancer TimeOut for Cloud Service Roles (PAAS Web/Worker)
    Windows Azure Load Balancer Timeout Details
    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/89b283f0-dfca-49a7-99fe-c3b73d77ff6d/azure-load-balancer-sending-http-request-to-multiple-web-role-instances?forum=windowsazuredevelopment
    If I misunderstood, please let me know.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Change basicHttpBinding to wsHttpBinding in azure cloud service web role

    So I created a cloud service project in visual studio and added wcf service web role to cloud service.
    By default wcf service web role binding is set to basicHttpBinding.
    Currently my web.config looks like this:
    <?xml version="1.0"?>
    <configuration>
    <system.diagnostics>
    <trace>
    <listeners>
    <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
    name="AzureDiagnostics">
    <filter type="" />
    </add>
    </listeners>
    </trace>
    </system.diagnostics>
    <system.web>
    <compilation debug="true" targetFramework="4.0" />
    </system.web>
    <system.serviceModel>
    <behaviors>
    <serviceBehaviors>
    <behavior>
    <!-- To avoid disclosing metadata information, set the value below to false before deployment -->
    <serviceMetadata httpGetEnabled="true"/>
    <!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
    <serviceDebug includeExceptionDetailInFaults="false"/>
    </behavior>
    </serviceBehaviors>
    </behaviors>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
    </system.serviceModel>
    <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
    <directoryBrowse enabled="true"/>
    </system.webServer>
    </configuration>
    How do I change my config to use wsHttpBinding?

    Hi,
    Please refer to
    http://msdn.microsoft.com/en-us/library/ms733099.aspx. From my experience, in Windows Azure, we cannot use Windows authentication (the default configuration for WSHttpBinding), unless we use WAAD and let the cloud server join the local domian. So it is
    needed to turn off authentication, or use an alternative authentication mechanism (such as username and password).
    Best Regards,
    Ming Xu
    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support
    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Maybe you are looking for