Since 2019 Custom Resource Providers are still in public preview, this prevents partners and organizations to put bigger investments in creating additional services on the platform as the service capability might be removed, changed or never be supported.
Is there any outlook by when the service might be released/published? If not at least some sort of roadmap, what is missing to get it there?
I've checked the documentation and GitHub Issues, but there is not much movement on the CustomServiceProvider portion of Azure.
Related
Currently based on https://github.com/Azure/portaldocs custom Azure Blades can only be developed internally within Microsoft Product Groups, however they are using React Templates to provide a customized view for custom resources. Ibiza Extensions (Codename for the Portal) would be a great extension on top of custom resource providers.
Is there any capability to onboard resources from organizations, which published their service through the marketplace and/or partners after going through the official onboarding process?
I've checked through the https://github.com/Azure/portaldocs documentation to understand the process and details on how to get engaged. The repository however does not intake any issues to ask there.
Currently we don't have any plans around extension development in our roadmap in the near future. In general, we would prioritize against existing backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once any feature request is addressed.
When deploying resource in Azure, the default location is always Central US.
Is there any way to configure a preferred location? I cannot find any documentation about this.
It is not supported as of now. It could be due to few reasons a company might prefer deployments across various regions and different subscriptions.
However if you badly need this upvote this uservoice
When deploying the resource in the portal, it will not choose the preferred location for you automatically. But you could choose it manually by yourself, generally, we consider it from compliance to resiliency features.
To find the Azure geography that meets your needs, you could follow this link.
https://azure.microsoft.com/en-us/global-infrastructure/geographies/
We currently have an Azure account set up through a third party who happens to be a CSP. As expected, this took several hours to set up and configure.
We're looking to move from that CSP partner to an account that we manage ourselves. The feedback we're getting is that that's not something easily done.
Has anyone experienced difficulties moving from a CSP to a pay as you go subscription, or is this company we're dealing with holding something back? I obviously want to avoid the several hours of re-setting up all of our resources.
Migrating resources across accounts are not something I have seen done. But you may get the Azure resource manager template for each resource. See attached link.
At the same time I would encourage you to implement infrastructure as code as part of your best practice for development in your organization. Infrastructure as Code is a process of managing and provisioning computing infrastructure in Azure with some declarative approach while setting their configuration using definition files instead of traditional interactive configuration tools.
The key benefits of IaC are:
Consistently achieve standardised provisioning or deployment
Accelerating provisioning or deployment rapidly
Reusable JSON code for repeatable or similar provisioning or deployment
Extensible JSON code for incorporating with additional items
Export template: https://learn.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-export-template
Infrastructure as code: https://blogs.msdn.microsoft.com/azuredev/2017/02/11/iac-on-azure-an-introduction-of-infrastructure-as-code-iac-with-azure-resource-manager-arm-template/
Am trying to help a customer move their services from an Azure Direct subscription to a CSP subscription. In the guides I've found, the approach used for IaaS1 (the old/class Azure - ASM) differ from what's used if a client's services all belong to IaaS2 (the new portal - ARM).
My confusion arises from the fact that while things like Class VMs can be easily identified if one views a client's services under the new portal - they are annotated as "Classic", am not so sure about any other services originally created under the ASM model.
And to further complicate things, it seems as though, viewing a client's services in the classic portal shows both ASM and ARM services, and this, without any means of distinguishing between them!
So, how do I go about this?
I maintain a family web site on Azure on my spare time. For a small fee, we have purchased a custom domain name to make it more "professional".
Unfortunately, the credit card associated with the susbscription has expired and since I was not actively monitoring the dedicated mail account I had created for this purpose, the susbscription has now been deleted (the susbscription is actually disabled in the portal, but the mail from Azure says that I need to create a new subscription if I want to change my mind).
In a matter of minutes, I registered a new subscription and thanks to continuous deployment, I could deploy the Web App from sources that I had kept on a GitHub account. However, an attempt to bring an external domain to the Web App fails with the reason being that the said domain is already in use by another Azure web site (presumably, the old Web App from the, now deleted, subscription)
A quick chat with the #AzureSupport team on Twitter, they suggested I file a support request from the Azure portal. However, since this is not a professionnal susbscription, I do not have a support plan. I see that support costs 25 $/month for at least 6 months in my situation.
This seems a bit too costly, like an order of magnitude higher than buying a new domain name for several years. At the same time, I don't understand why the deleted account is still locking the custom domain name. And it seems unfair that I need to pay to recover a domain name that I own but am unable to benefit from because it is associated with a Web App in a disabled Azure subscription!
Please, what are my options?
PS: Even though this is not a programmatic question, I post here because that's where Microsoft recommends to obtain community support. I have also posted a similar question on an appropriate MSDN Forum but the answers there are not satisfying.
Unfortunately on a technical level this will be something that can only be rectified by Azure support. Since you no longer have access to the account they will need to delete that domain association.
It is excessive that you are required to pay for a six month support contract to resolve an issue that is clearly an issue with the way Azure decommissions subscriptions.
The problem you now have is that you can't use Azure to host this domain until that association is removed. Your only options are to either have the complexity of using a VM or to move your site to AWS etc.
If you make those points to #AzureSupport team, maybe they will process it for you. Point them to this question and ask them to help you to keep using Azure.