Video

@@Mexoi thanks man!

Thanks! Yes, a drone gives you a very special perspective 😀

Thanks for your kind words! Love your channel and started to follow it!

'Host' is the host name where your API lives. It's the URL part without ''. In this example I entered the host name of my Ngrok tunnel (ngrok.com/). Ngrok is a reverse proxy and allows you to open a port to your machine so that it's accessible from the internet. It's also free, with some limitations. Very useful if you're building stuff to integrate with the cloud. These days I'd probably use the built-in Dev Tunnels feature of Visual Studio, which does more or less the same.

​@@sanderschutten Hi! Thanks for you response and sorry for my ignorance. I still dont get it. I'm using the connector "When an HTTP request is received" and pasting the Json schema of the webhook I get an URL automatically. Then, I register this url in GUPY, where I want to monitor the webhook, and thw flows works as it should. What if I want to use a custom connector to do that? Do I need to create and host an ednpoint anywhere?

@@anacarolgomesr Not a problem, perhaps it is just me not understanding your question 😊 You mention you use the "When an HTTP request is received". That's the typical HTTP trigger to start a logic app or flow. If your requirement is to start the logic app/flow from a webhook from GUPY, that's the way to go (sorry, don't know GUPY, but looks like some HR system?). It's very much possible to do that with a custom connector, but yes, that requires you to create and host an endpoint. However, there must be a good reason to go that route, because it's relatively complex. One thing that I can think of is that you want to make it easy for power users to response to webhooks in GUPY, but don't want them to register webhooks in GUPY themselves, e.g. because of permissions etc. May I understand your requirement for a custom connector, so I can better understand what you're trying to achieve? I've a (lengthy, sorry) video showing how to create an API to perform the webhook actions here: czcams.com/video/ECiurSHU_lM/video.htmlsi=1w87r46iz1edn1Id&t=4892 in case you're just looking for that.

​@@sanderschutten Hi! Thanks again for your time and your help! :) In my company we have a policy of creating custom connectors to limit the use of these connectors, so if I create a custom connector for this purpose, its user could only use it for this specific context. I was hoping there was a way to create a url automatically in the same way as "When an HTTP request is received" connector. But unfortunately the way to do this is more complex than imagined, right? Gupy is job application platform. The Webhook is triggered every time a person applies for a job. I configured the url generated by the "When an HTTP request is received" connector on the platform and the flow is working correctly. I expected to do the same thought custom connector...I saw something in Microsoft docummentation about using GItHub to do that but I couldnt understand.

@@sanderschutten Your comment was very helpful! Thank you very much! 😀

Nope, it won't. If you need to do that you need to break it into two steps: first load all the secrets into a Powershell variable, then switch to the other subscription and add the secrets from the variable.

Not from my hand there isn't. Drop me an e-mail at sander [at] dotnetstudio.nl with your problem and I'll try to help you.

Event grid is not required, but you could use it if it fits your requirements. What the webhook trigger does is it sends your API a request for registering the webhook. The request contains a callback URL where Logic Apps expects to receive the events. In your API you store that callback URL and whenever an event occurs you post that.

In your scenario it would look something like: my app -> event -> event grid -> azure function with event grid/http trigger -> POST to callback URL -> custom connector.

@@sanderschutten Cool, thanks for making me understand that Sander. Will get back with an update!

Thanks for the feedback! I'll take this with me for a next video.

What do you mean?

@@sanderschutten first of all it's hard to see what's on the screen, because of low resolution. Also much time spent for showing development job, but without final result. For example I had to switch to swagger and do some manual changes, visual designer didn't highlight an error. So would be useful to see if the trigger was finished and successfully sent webhook when used in flow of logic app.

@@poplutinBl I see what you mean. Thanks for the feedback. When I do a new video I'll take a look at the resolution. This is a piece from a live coding session that I highlight here. Maybe the full video is useful for you where you can actually see the webhook trigger. You can find it here: czcams.com/video/Uis4TGnmZwk/video.html. I know it's a bit lengthy.

From this point you can see how the webhook is triggered: czcams.com/video/Uis4TGnmZwk/video.html

Not as far as I know. I just checked, but I still see 'Triggers' on the '3. Definition' page. Are you sure you're on the correct page?

Triggers option is only available if you are creating the custom connector from Power Automate. if you are doing it from Power Apps Trigger option will not be available.

I don't know why the options are different for some flows. It could be that you use flow specific actions. For example the approval actions only exist for flow, not for logic apps. I mostly use logic apps instead of flow, so I can't help you much further.

Even I am also facing same issue

Thanks! I agree, the addition of managed identity for the Key Vault is very welcome (and overdue) addition. Way easier :)

This script assumes the key vaults are in the same subscription. Connect-AzAccount on line 4 connects to your default subscription. If you need it to work between key vaults you need to break the script up into two pieces: 1. Where you store all secrets in a local dictionary variable 2. Where you switch to the different subscription and write all the secrets from the dictionary variable to the destination key vault I don't have a working example script for you, but hopefully you can work it out using these pointers.

Hi Alexandra! It's been a while since I recorded this. What password textfield do you mean exactly?

@@sanderschutten I have a form in the chatbot for the user to register, so for example: ID: Alexandra Password: alexandra123 But I want the password to appear "*******". Like this: ID: Alexandra Password: ******** I hope you understand me, I am using a translator since I really speak Spanish hahaha :(

@@sanderschutten :( Help please

@@alexandragallardo5851 This can't be done at the moment. The team is considering supporting it for a future release, as can be read here: github.com/Microsoft/AdaptiveCards/issues/1443. Your best option is to use the OAuthCard as described here: docs.microsoft.com/en-us/azure/bot-service/bot-builder-authentication?view=azure-bot-service-4.0&tabs=aadv2%2Ccsharp. However, that would require Azure Active AD authentication.

@@sanderschutten Oh I see, I will try to implement OAuthCard, thanks for answering me!

Hi Guillermo! That's indeed an option and exactly the reason I started building the conversations in Logic Apps! Currently we're reworking our bot to use The Bot Framework Composer to create the dialogs, but we still call a logic app to do the actual integration with e.g. Dynamics CRM and AFAS.

You sure can. I don't know why you lost the SAS token, but if you store it correctly it should work just fine.

Not sure if script accounts for that. I think it assumes the keys don't exist in the destination, but you can try. It's mostly a tool for quickly moving your keys to a new key vault.

The Set-AzKeyVaultSecret will override the value in the destination key vault. If that's not something you want you should check the existence of the secret first e.g. by calling Get-AzKeyVaultSecret on the destination key vault and verify if you get a value.

I don't think there's a similar solution for .NET Framework 4.7 project as they use a different configuration method.