Soporte técnico de la comunidad de Azure

Formule preguntas, obtenga respuestas y comuníquese con los ingenieros de Microsoft y los expertos de la comunidad de Azure

Productos

    Foro de MSDN

    Respuesta de Microsoft a las preguntas técnicas sobre Azure

    1. Más recientes
    2. Popular
    3. De tendencia

    Response issue using portal

    Forum: Azure Virtual Machines

    Help to open ports.

    Forum: Azure Virtual Machines

    StackOverflow

    Respuestas de la comunidad a las preguntas de desarrollo

    1. Más recientes
    2. Popular
    3. De tendencia

    How to HTTP to an Azure Virtual machine?

    • node.js
    • azure
    • azure-virtual-machine

    How to connect AzureML (Machine Learning) with AzureVM (Virtual Machine)?

    • php
    • azure
    • azure-virtual-machine
    • azure-machine-learning-service
    • azure-notebooks

    Serverfault

    Respuestas de la comunidad a las preguntas de administración de Sys/Net

    1. Más recientes
    2. Popular
    3. De tendencia

    Comentarios de Azure

    ¿Tiene alguna idea o sugerencia basada en su experiencia con Azure?

    1. Más recientes
    2. Popular
    3. De tendencia

    creation of public private key pairs on the portal

    When deploying a new Linux based VM, create a shortcut to create a SSH keypair and download the private/public key straight from the portal... saves downloading puttygen or similar..

    B Series Burstable Unlimited Mode

    The B Series family should offer an "Unlimited" mode for bursting. So when a workload runs out of credits to burst, if the mode is set to unlimited, the vm will be billed at higher rate instead of just dropping down the allowed average. (Like the AWS featuer for T3)

    Creating a Low Priority VMSS using Portal has FD count bug

    When creating a VMSS with Low Priority, FaultDomain Count is set to 5 by default. "spreadingAlgorithmPlatformFaultDomainCount": { "value": "5" Obviously this is a bug, because Low Priority VMSS only supports Single Fault Domain https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority If we go with the default value, we got FD count error. Deployment failed. Correlation ID: { 'error': { 'code': 'InvalidParameter', 'message': 'The value of parameter platformFaultDomainCount is invalid.', 'target': 'platformFaultDomainCount' } } I think this needs to be fixed in Portal Front-end side.

    resize VM without reboot

    Currently if you want to change the VM Size of Azure, VM is restarted. VM Resize shouldn't require downtime and it should be done in the backend. As CPU and RAM is still throttle when we use more resources then why can't we just remove the throttling limit and inform customer that VM is resized from A to D series when request is raised of resize?

    Abra una incidencia de soporte técnico

    Crear un incidente

    Envíenos un tweet a @AzureSupport

    Conectarse a Twitter

    Ayúdenos a mejorar. ¿Le resulta útil esta página?

    Límite de 160 caracteres