Azure Api Connections: Change the connection name - azure

I created a couple of Azure API connections and it allows me to change the display name, but there is no way to change the name itself. Apparently, it automatically creates the connections based on the connection type. Is there a way to control this?

Yes, you could deploy API connector and change its name with Template. If you already have a API connector, click it then choose Automation script and click Deploy.Like the below pic shows.
Now choose Edit template and for convenience delete the parameters and resources you don't want to use. In here you could change defaultValue as the name ,after modify the template would be like the pic shows, then click save. I fthe name in SETTING is not changed you also could change it here.
And the result shows the API name is not the original default name.
Note: This way is only used to deploy the API connectors.
Hope this could help you, if you still have other questions, please let me know.

Related

Lookup Azure application name from within a running function app

Is it possible to lookup the application name for an Azure app as it runs, i.e., get the information about that is displayed in the Azure portal? In the example below, I'd want something to tell me from within the application that I am running sitemap-prod-eastus.
I've been looking at the Azure Context object but not seeing what I need. There is an invocation ID, a name for the function, a directory - not the info in this window.
Maybe this can be done through Azure Application Insights?
I am working in Node JS.
I've not seen anything that would expose this to a function app. That said, there is one sort of workaround that you could do which would work - go to the Configuration blade for the function app, Application settings tab, and add a configuration key like function_name and set its value to the name of your app. Your app could then just read it out of configuration.
It's an extra step, but if you're doing it with something like ARM or Terraform, it's just another configuration entry with a variable you already declared to set up the app in the first place.
Answering my own question: Azure provides WEBSITE_SITE_NAME in the runtime environment that matches the name of the function app.

Azure Logic App SubscriptionNotFound error

With the intention of building a generic logic app solution via Azure Portal, I've supplied all config to the logic app connectors as parameters sourced from a database.
The only problem I've experienced now though, is that the custom value supplied as the subscription for the ADF pipeline run is not working. The exact same value works when selected explicitly from the dropdown. The other values such as the Resource Group, Data Factory Name and the Data Factory Pipeline Name work fine when populated by the parameters.
Is there a specific way to do this? Or is this a bug in the Logic App ADF connector?
Please do not put the name of subscription into the Subscription input box, it can not be executed success. You can put the subscription id into the Subscription input box, show as below screenshot:

Azure APIM VNet Stuck

I've created an instance of APIM. After placing it in a Virtual Network, when I click on API's It just sits there spinning. If I click add, and attempt to add a new API I get the following error message no matter what "Name" I give it. "One or more fields contain incorrect values:
Name is already in use"
There are no API's so this should not occur at all, for the sake if testing I tried several random strings and it's always the same response.
Any thoughts?
Please refer the important section in the enable vnet connection article.
https://learn.microsoft.com/en-us/azure/api-management/api-management-using-with-vnet#-enable-vnet-connection

Service connection creation operation failed in Azure devops

I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.

Let's Encrypt: ClientID reqistered under application settings differs from what I entered?

So I am trying to get Let's Encrypt working on Windows Azure through the web extension but I am getting a error that I cannot solve or find any information about.
I am following this tutorial on how to set ut Let's Encrypt on Azure:
https://github.com/sjkp/letsencrypt-siteextension/wiki/How-to-install#create-a-service-principal
When I use the extension wizard, fill in all the fields and press next this is the error I get:
My resourcegroup:
My serviceplan inside my resourcegroup (+ storage and app service):
My ClientID (application id):
My secret is also set, saved the value and pasted it into the wizard:
My connection strings are set (in the format mentioned in the tutorial/setup):
There is a webjob running, I did not create this, I think it was created by the wizard in some way(?):
And at last:
It seems to me that I have done everything the tutorial has asked me to do, I don't know why I get the error, I also don't understand the reference to "00000000-0000-0000-0000-000000000000". Does anyone know what I did wrong and how to solve this error?
Thanks in advance.
The checkbox "Update Application Settings" must be checked if you want to modify the settings from the Let's Encrypt extension's pages.
If you hate the idea of an azure webjob swallowing valuable system resources of your azure app service then there is now an alternative solution which uses Azure Automation;
https://www.powershellgallery.com/packages/GetSSL-LetsEncrypt
Documentation # https://w.itpro.es/ssl-eng

Resources