i can’t for the life of me figure out how to create an enterprise edition agent.
this is the only documentation i’ve found about it: https://cloud.google.com/dialogflow-enterprise/docs/quickstart
which seems to imply that we’d need to set up agents using the command line… for them to be on Enterprise Edition.
any insight? i'd like to create an enterprise edition agent - so that it's covered by the SLA. how to do it?
Did you click the section expansion button to the left of "If you have not created an agent, create one now."?
Edit: the below procedure will only work on Google Cloud project not created through Dialogflow.com. The only way to create a enterprise edition Dialogflow agent is to first create a GCP project and then follow the procedure below. You can't create a enterprise edition Dialogflow agent through Dialogflow.com (but you can access it on Dialogflow.com after creating it via the procedure described below).
Go to http://console.cloud.google.com/apis/library/dialogflow.googleapis.com/ (create a project if you haven't already, you can only have one Dialogflow agent per cloud project) and enable the Dialogflow API
After the API has been enabled click on Dialogflow Agent in the left column
Specify the name of your agent and other properties such as language and time zone, and then click Create
This is documented here (you need to click on the ▼ to see the documentation): https://cloud.google.com/dialogflow-enterprise/docs/quickstart#create-an-agent
Related
I have a single-tenant logic app and a workflow under it that needs a configurable input. In a multi-tenant logic app, one can define parameters through the azure portal and reference them in workflow definition (actions/ triggers). Is this not possible with a single-tenant logic app?
I am not able to find the answer in the documentation.
I know a deployment template should consult parameters file for this, however, I still have the above question specifically if I am doing stuff through the portal.
Edit 7/12
I am referring to the parameters concept explained here, and not the parameters tab of the triggers or actions. See below the parameters that we can define through the portal when working with the consumption logic app.
The answer is: not yet. Support for parameters in the designer (and therefore in the Azure Portal) is on its way, but not available yet.
In VS Code, you can create a parameters.json file.
But in the portal, there's no option (yet) to create/edit parameters.
Bec Lyons (Microsoft) demoed a version of the designer with this in it, although I can't remember if this was in the June Logic Apps Live session, or in the July Integration Down Under session.
In any case, the only currently supported way to do this is to create a parameters.json file and upload it.
You can either do this from VS Code or Azure CLI (using the preview logicapps CLI extension) OR you can FTP to your Logic App and upload it via an FTP client (e.g. FileZilla) - you can get the FTP login details by clicking the "Get Publish Profile" button in the overview of your Logic Apps Standard resource.
Once they release support for this in the Portal/Designer, I'll update this answer.
Also, worth noting that as of this date (July 2021), there are issues using parameters in Managed API Triggers - not sure yet if this is by design, or if it's a bug. Specifically the FileSystem, FTP and FTPWithSSH (SFTP) triggers.
Hope this helps. Probably not the answer you were looking for, though!
I am trying to automate VMs onboarding process for Azure Update Management. I am wondering if it possible, I didnt find solution which I can use to full onboard VM to Update Management, from A-Z. I mean I need MMA agent installation (i have script prepared, for installing mma vm extension with workspace ID and Key). Problem is that thare I didn't find a way to perform rest of the steps. Did anyone try to do this, I know that Ms give the runbook form this but I am not sure if its working as expected, link here --> https://learn.microsoft.com/en-us/azure/automation/update-management/enable-from-runbook
You can automate it by configuring UM to automatically enable for all existing and future VMs using this method - Enable Machine in the workspace
But keep in mind that using this method doesn't allow you to have the control an enterprise customer would want.
We don't have an out of the box method to configure from the VM, onboarding it to UM in an automated manner. Based on how it is designed, the only way out of the box is from the portal, or runbook as described in docs.
Programatically to work around this (and I'm thinking out loud here) you could update the saved search query - MicrosoftDefaultComputerGroup in the workspace with the UUID of the VM and that would automate onboarding it to the feature. I don't have a working example to share but I think the approach is sound and can be included in the workflow to onboard it.
I am unable to create a new Dialogflow agent through the console. When I select the agent's name and click on "Create", the button changes to "Working" for a few seconds and then says "Cancelled".
Any help is appreciated.
Thanks.
There are could be a few reasons for that:
You have selected the wrong Could Project. GCP limits one agent per project, you cannot select a project that is already connected to Dialogflow
If you are creating a new Google project for your new agent, you probably have reached your limit with projects per billing account. You can check this by disabling billing for some of your projects and try to create again.
There are some limitations for naming agents as well [here]
I'm trying to create a bot using the Azure Portal, trying to follow some tutorials from the documentation. Specifically, these:
Microsoft Docs https://learn.microsoft.com/en-us/azure/bot-service/abs-quickstart?view=azure-bot-service-4.0
Azure 4 Everyone https://youtu.be/-FHc_lZ6jJY
When I got to the Azure portal and try to create a Web App Bot however, I am unable to choose a template. It seems to assume I want to create a QnA Bot, which is not the case. I've been doing tutorials and research for a few days; I'm pretty sure I recall this was not the case as of yesterday.
Did something get updated? Is using the Visual Studio template my only option now? I was hoping to use VS Code for the development once I downloaded the basic bot template.
Edit: I include a screenshot here of the blade I get when clicking "Create" on Web App Bot in the Marketplace.
URL: https://portal.azure.com/?Microsoft_Azure_BotService_subscriptionId=a2096f22-5a26-42bf-962a-aa232ff81cfe&Microsoft_Azure_BotService_qnaHostName=qna-testbot-001.azurewebsites.net&Microsoft_Azure_BotService_qnaKbId=87f53208-171f-4323-9905-3257bef5cdf3&Microsoft_Azure_BotService_csResourceGroupName=rg-bot-dev-001&Microsoft_Azure_BotService_csAccountName=qna-testbot-001&botsvc.rp=true#create/Microsoft.BotServiceSdkGalleryPackage
Looks like some folks might just be getting the wrong link in the Azure Portal for some reason. This one should work.
You should be able to choose from:
C# or Node, then
Echo Bot or Basic Bot
In the Azure Portal, click "Create a resource"
In the search bar, type "Web App Bot" and click Create
Then select the appropriate bot under Bot template
Alternatively, you can start with any of the samples, which offers a much much wider selection of starting points.
hoping someone has seen this before.
When I try to enable continuous integration in Visual Studio, using Visual Studio Team Services, I get the following error:
"This version control host is unsupported. Repositories must be hosted on VSTS or GigHub." This error gets zero results in google.
As you can see in the screenshot, the solution IS hosted by VSTS.
Explaining the screen shot:
Section 1 in the pic is the pop-up that appears after clicking 'Configure Continuous Integration' in the VS2017 status bar.
Section 2 is my VS team explorer window.
The grey boxes are the company website 'mycompany'.
Additional facts:
The VSTS account is owned by admin#mycompany.com, but my dev account, jason#quantumland.com, has full contributor permissions to the project. I get the same error whether red box 1 above has my personal account selected or admin#mycompany.com
The current loaded solution is the basic starter '.NET Core Web application' in VS2017 Community edition. No authentication selected, no changes to the auto-generated code.
I can build and run the solution locally, check in the solution to VSTS, see the code in the VSTS repository, publish to Azure web app, etc. Everything seems to be working but this.
Appreciate any help. My best guess is that my security permissions are wrong in VSTS, but both accounts are members of the 'admin team' group, and admin#mycompany.com is the creator/owner of the VSTS account and repository, so I don't see how.
You are using TFVC version control, the continuous delivery is used for Git version control, so you need to add a new git repository (can be in TFVC team project: Use Git and TFVC repos in the same team project), and use this git repository as source control.
Article about TFVC and Git: Choosing the right version control for your project
I was able to use TFVC for version control and get CI/CD to work. Following the newer instructions provided by #starain-MSFT:
Continuous Integration
This sets up CI/CD using the VSTS web portal exclusively. It works, but if I click 'configure continuous delivery' in the VS2017 status bar and use that form, I continue to get the error above.
If anyone posts an answer that fixes the exact question asked I'll update and mark that as the answer. Good news is that you can indeed use TFVC with CI/CD. yay, and thanks to #starain-MSFT for the updated link.