by Contributed | Apr 4, 2023 | Technology
This article is contributed. See the original author and article here.
To increase our developer experience landscape and to allow customers to interact and extend Microsoft Purview functionality using software technologies and tools in their organization, we are happy to announce that REST APIs and SDKs for workflow data plane in public preview. Software engineers or developers in your organization can now leverage these APIs/SDKs to programmatically create or update a workflow, submit a workflow, approve or reject an action, update or re-assign an approval or task action, list or cancel workflow runs, and more.
In order to use any Microsoft Purview data plane APIs you need to first create a service principal and assign it to the right Microsoft Purview role before invoking the APIs. This is needed to establish trust between the service principal and the Microsoft Purview account. For example, to create a new self-service data access request workflow and bind the same to root collection, you need to provide ‘Workflow Admin’ role to the service principal at the root collection level.
This tutorial covers details on how to create service principal, set up authentication using the service principal, get token and use the token to call Microsoft Purview data plane APIs.
To get started with workflow data plane APIs and SDK’s please see the below links:
- Workflow data plane APIs, see here.
- Workflow data plane C# SDK, see here.
- Workflow data plane Java SDK, see here.
- Workflow data plane Python SDK, see here.
- Workflow data plane Java script SDK, see here.
by Contributed | Apr 3, 2023 | Technology
This article is contributed. See the original author and article here.
In this issue:
Welcome to Logic Apps Aviators Newsletter – April 2023, the official monthly newsletter for Microsoft’s Logic Apps Aviators community. Catch up on Microsoft news from us and our community.
News from our product group:
|
Logic Apps Aviators Day
On June 22, 2023 (Pacific Time) the Logic Apps Product Group will host a full day of learning where you will be the start! The Logic Apps Aviators is a free event driven Microsoft, for anyone who wants to learn more about Logic Apps and how it can help to solve real life integration problems. In this full-day event, we will deep-dive into many aspects of Logic Apps with sessions from both Microsoft team and community. And we are looking for sessions of all types, from beginning to advance, from patterns and practices to real life scenarios.
|
 |
Logic Apps Live – Community Standup (March 2023)
In this recording we will discuss the new Application Insights (Preview), IBM Host File (Built-in connector), Logic Apps Designer and Connectors 101 presentation.
|
|
Application Insights Enhancements for Azure Logic Apps (Standard) – Preview
We have recently published an update to how we emit telemetry for Application Insights in Azure Logic Apps (Standard). This new update is currently in Public Preview and is an opt-in feature for customers. It can be enabled without introducing risk to your telemetry. For customers who choose not to opt in, they will continue to emit telemetry using the existing method.
|
|
Improve Logic Apps (Standard) Workflows Observability with Application Insights
InfoQ.com, a popular technology publication, recently picked up coverage about our Application Insights (Preview).
|
|
Extending Logic Apps App Insight integration with Azure Workbooks
In this blog post we are going to show how we can use Azure workbooks together with recent improvements to application insight integration to build similar rich and interactive dashboards for standard Logic Apps.
|
|
Integrate Azure Open AI in Teams Channel via Logic App
Now in Azure, we can deploy Open AI with chatgpt-35-turbo model as an Azure resource, so this blog introduces how to integrate the Azure Open AI in Teams channel without using a bot.
|
|
Using Logic App Standard to connect to SAP
Learn how to setup SAP connections in Azure Logic Apps (Standard).
|
 |
Deploying Logic App Standard resource using Bicep templates and DevOps pipeline
In this blog, we will explore the creation of Logic app infrastructure components using Azure Biceps template. Bicep is a domain-specific language (DSL) that uses a declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to deploy your infrastructure repeatedly.
|
|
Attaching a file to a DevOps Work Item
How to create the actions to Attach a file to a Work Item in DevOps, by using the Azure Connector.
|
News from our community:
Logic Apps and DocuSign integration
Post by Sandro Pereira
DocuSign is used by individuals, businesses, and organizations of all sizes across many industries, including finance, real estate, healthcare, and more. The platform streamlines the document signing process and eliminates the need for physical documents and manual signatures, which can be time-consuming and costly.
Get notified on expiring Intune LOB apps
Post by Peter Klapwijk
Set up a Logic Apps workflow to get notified when an iOS LOB app is about to expire. An expired iOS LOB app can’t be deployed to our users anymore, so we need to make sure the apps are renewed before they expire.
Network Security for Integration Projects
Video by Paul Baars
Paul Baars talks about network security for integration between on-premises systems with the Azure Serverless cloud.
Modernizing Consumption Logic Apps with Bicep Infrastructure as Code (IaC)
Video by Mitchell Abel
Bicep has made creating the resources a lot simpler and less verbose. And the separation of Infrastructure and Code with Logic Apps Standard has made the day-to-day way of working, especially when the integration developer is responsible for their own DevOps, a great deal easier once everything is set up.
Azure Logic Apps: KQL for having an overview of your scheduled workflows
Post by Stefano Demiliani
This post answers some questions Stefano had from customers, including:
- Is it possible to have an overview of all the workflows I have (and their state) across subscriptions?
- Can I know the connectors they’re using?
- For timer-based workflows (recurrencies) can I have an overview of the scheduling?
Remove Azure Logic App Orphan Metric Alerts
Post by Mark Brimble
A quick tip showing how to remove orphan metric alerts from deleted Logic Apps consumption.
by Contributed | Apr 1, 2023 | Technology
This article is contributed. See the original author and article here.
While many folks observe April 1 as April Fool’s Day, we in the SQL Tools team celebrate April 1 as April Tools Day, a day when we debunk myths surrounding the tools for SQL Server. We recommend having some good chocolate to honor the occasion.
Now, you may wonder how we are aware of the misconceptions that exist for the different tools for SQL Server. Some thoughts we hear from direct conversation, for example at conferences and on social media. But one of the best resources is the comments that folks leave when responding to a survey.
For example, you may have been using Azure Data Studio and had a dialogue pop-up that asked if you would recommend ADS to a friend. While we would love for folks to provide a 9 or 10 when asked, what’s more interesting are the comments shared after selecting a score. We read every. single. comment. that is entered. These replies create a picture of what users find challenging and what they would love to see, and ultimately they help us make the product better. They also reveal misunderstandings that exist about a given tool, which leads to our celebration of April Tools Day.
Myth #1 Azure Data Studio is the only standalone solution now that SSMS is deprecated.
SQL Server Management Studio (SSMS) is not deprecated. We thought about writing that in ALL CAPS, but figured bold is sufficient. SSMS has not been deprecated, and we are not planning on deprecating it. You will see new functionality being added to Azure Data Studio, but we have a fair number of things lined up for SSMS, including migration to the Visual Studio 2022 shell, which brings 64-bit support.
Myth #2 No new work is happening with drivers.
You may have missed the debut of the new sqlcmd (aka go-sqlcmd) a couple weeks ago during the SQLBits conference. This tool is based on the Go driver mssqldb. The new sqlcmd is still in preview, but version 1.0 will GA soon, and in time we expect it to replace the existing sqlcmd while also surpassing it in capabilities. For example, it can be used on Linux and Mac, as well as Windows, can be quickly downloaded or updated, and works for Azure SQL Database and on-prem installations of SQL Server. Once you have it installed, run ‘sqlcmd create mssql’ to create a SQL Server container based on the latest image – it’s that easy. If you want to learn more, check out the documentation or the GitHub repository. (Yep, it’s open source, too.)
Myth #3 The SQL Database Projects extension features are lacking.
We have made significant strides in adding functionality to the Database Projects extension. With GA on the horizon, the extension will sport a new backend and in time will include new features such as moving/renaming files, saving publish profiles, and more. We also will have a brand new Microsoft.SqlServer.DacFx.Projects nuget package that supports programmatically editing SQL projects wherever you want, including CI/CD pipelines!
Myth #4 Azure Data Studio runs slower on Mac and the functionality for the Linux-based version is much less compared to the Windows version.
If you’re using macOS or Windows on a machine with arm64 processors, make sure you are using the native build of Azure Data Studio, highlighted with the yellow arrows in the screenshot below, for optimal performance.
Azure Data Studio Install Packages
In the most recent release, ADS 1.42, we added native arm64 SqlToolsService support for arm64 Windows and macOS. Fun fact: the SqlToolsService (often abbreviated STS) is what provides SQL Server support in Azure Data Studio.
Further, the functionality in Azure Data Studio is the same across all platforms: Windows, Linux, and macOS. There is no feature or capability that is “different” or “less” for any operating system.
Myth #5 In Azure Data Studio, on the Connections pane, the Servers are currently at the database level, so each database has to be connected separately. Ideally, the full Server could be traversed within the tree (similar to SSMS).
In Azure Data Studio, you have the option of connecting to a server (e.g. on-premises or SQL in an Azure VM) or connecting to the database directly. You configure this within the connection. In the first screenshot, we connect to a local server (SQL2022 is a named instance):
Screenshot of connection configuration for server
Note that we named the connection “Connect to server”. Next, we’ll create a connection for a specific database, WideWorldImporters:
Screenshot of connection configuration for database
This connection is named, creatively, “Connect to database.” When we look in the Servers view, we see both connections:
Screenshot of server view with server and database connections
The “Connect to database” connection only shows Tables, Views, etc. in Object Explorer for the WideWorldImporters database, while the “Connect to server” connection shows the Databases node, as well as other server-level nodes, just as you see in SSMS.
Myth #6 The hardcoded 45 second object explorer timeout is a huge pain in my *readacted* and a horrible design choice. No competent engineer would implement something like that for a SQL server interface.
Good news! Thanks to our competent engineers ;) we added the ability to increase that timeout in Azure Data Studio 1.42. Within Settings ( CTRL/CMD + , ) search for expand timeout to see both an Object Explorer timeout setting, as well as one for the Server tree:
Screenshot of timeout settings
Modify those as needed! There is also a new Command timeout in the Advanced pane of the Connection dialog, just below the Connect timeout.
Myth #7 One of the key tools I still use from the SSMS program that is missing (as far as I can tell) from Azure Data Studio is the ability to use the table designer to modify existing tables.
Table Designer for Azure Data Studio was GA’d in November’s 1.40 release, and an existing table can be modified using Table Designer. Simply right-click on the table and select Design:
Screenshot of right-click option to modify design of an existing table
Table Designer will open, and from there you can add a column, add an index, create a new constraint, and more!
Myth #8 Grouping of schemas has unfortunately still not been implemented, otherwise very modern.
Oh hey, maybe you missed last week’s blog post about ADS 1.42 and the new Group by schema option? It’s here:
Screenshot of Group By Schema option
We could go on, but in the interest of chocolate that may melt soon, we’ll wrap it up. We hope this has been helpful for those of you that use any of the SQL Server tools, and feel free to add a comment below if you know of other myths that need clarification. As any good DBA would say, “Trust, but verify.”
by Contributed | Apr 1, 2023 | Technology
This article is contributed. See the original author and article here.
Azure Database for PostgreSQL – Flexible Server supports over 50 PostgreSQL extensions. We are also constantly adding new extensions to expand on the functionality provided by the PostgreSQL engine. Until now we have not been providing support for the most important extension from the Postgres ecosystem, namely pg_carbonara.
While many developers and DBAs are aware of PostGIS as geo routing extension for Postgres or pg_stat_statements to track slow queries, not many are aware of pg_carbonara, which can be seen as a mandatory extension for a lunch break that allows you to cook a real Italian carbonara. What pg_carbonara does is guide you with step-by-step instructions to cook the dish.
As many of our team members were sceptic to introduce this extension, claiming that most of the developers and DBA’s do not eat, they just drinking coffee all day long, we have conducted a cohort study on a population of 100k developers and found out to our surprise that 95% of participants DO EAT. According to the study result we decided to make pg_carbonara extension a default and preinstalled in all new Flexible Servers. Enjoy!
The following blog post about the pg_carbonara PostgreSQL extension is an April Fool’s Day joke. We apologize for any confusion or misunderstanding that may have resulted from the post.
At Azure Database for PostgreSQL, we are committed to providing accurate and reliable information to our customers. We take any miscommunication very seriously, and we assure you that this was a lighthearted prank that was not intended to mislead or cause any harm.
We appreciate your understanding and hope that you found the post to be a fun and enjoyable way to celebrate April Fool’s Day. As always, please do not hesitate to contact us if you have any questions or concerns.
Recent Comments