Question: In a MS Purview, how can we delete a Business Glossary or rename it? There may be cases where you incorrectly created a Business Glossary or you had a spelling mistake, how can we rectify that mistake?
I am unable to delete a Business Glossary in a MS Purview account. The document Create and manage glossary terms from MS Purview team explains how to delete Business Glossary Terms but not a Business Glossary.
As with most things in Azure, if you don't see the functionality you are looking for in the portal, you need to look at the REST API or PowerShell. Here is how to do it in the REST API.
https://learn.microsoft.com/en-us/rest/api/purview/catalogdataplane/glossary/delete-glossary?tabs=HTTP
As for PowerShell, I am not seeing any native cmdlets to delete a glossary but there is a tool on the Azure GitHub page that will allow you to make the REST API calls using PowerShell. You can view that here:
https://github.com/Azure/Azure-Purview-API-PowerShell
Related
I am looking for APIs to get list of run instances of a workflow on SharePoint Online.
From Microsoft documentation I can get list of workflows in the tenant.
https://learn.microsoft.com/en-us/power-automate/web-api
I would like to get all running workflows of a particular workflow, not only assigned to me
As far as I am aware that Web API does not have an entity for the cloud flow runs (only the desktop flow ones, which is the flowsession entity).
However, you should still be able to use the Service.flow.microsoft.com approach.
For example Stefan Strube has a nice blog on how to create a custom connector for this:
https://2die4it.com/2020/07/08/custom-connector-to-get-flow-run-history/
I'm having trouble with retrieving azure update management details programmatically. I couldn't find any REST API or CLI method to get the data from update management view. There were only powershell scripts.
These are the details I want to retrieve via REST API
As shown in below screenshot, currently I see only below highlighted REST API's that are related to update management. Here is the document reference for the same.
If these REST API's doesn't help to accomplish your requirement then if interested you may share it as feature request in this uservoice or feedback forum.
In general, Azure feature team would check feasibility of a feature request, prioritize against existing feature backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once a feature request is addressed.
On the other hand, with the help of this references, you may find the same information in update management related kusto tables which you can query with the help of this REST API.
Here is the reference link for the same issue which was addressed in Microsoft Q&A
I'm trying to migrate Azure Boards from one organization to another. I dont see any documentation from MS for org to org migration.
Thank you Hugh Lin-MSFT for providing the details. Re-iterating here for broader audience.
If you are referring to moving work items from one organization to another, you can use the Excel to export and import the work items to achieve this .
First, you need to create a query to get work items, then install the Azure DevOps Office Integration Tool in azure devops , in Excel click on the Team button and then New List to get data from Azure DevOps to Excel, and finally publish work items to destination organization.
For detailed steps, please refer to this blog.
In addition, another way is that you could think about using third party extension tool like the Migration Tools for Azure DevOps . You can refer to this similar case.
Hope this information helps.
We have 2015 tfs server with 8 collections to be migrated to azure devops i have tried Microsoft azure devops migration tool but it is considering each collection as single organization but we want to all 8 collections under one organization each collection has different projects
Is there any way to do this i have seen Microsoft documention but unable to get any perfect solution what should i do could some please gudie me regarding this
Microsoft's documentation is the canonical, correct answer. You aren't finding other solutions because none exist. There is no way to import multiple team project collections into a single Azure DevOps organization via any tooling whatsoever. There is no other option for a full fidelity migration; although other tools exist that can migrate some data, no tool can capture all of the data, and no tool can capture the data without loss of fidelity.
Simple put, organizations are the Azure DevOps equivalent of team project collections. Each organization represents a single collection.
We're completely upgrading our production and development environment from co-located boxes to an Azure implementation and we'll be developing using Visual Studio Online. Up until this point our dev has occurred on a Remote Desktop environment where developers were logging into Windows server and developing on that RDP box.
We want to set this up and we have some confusion about the Account types/set up types.
It appears there are two ways to set up our Azure and two ways to set up our developers. We are a MS partner w/ some MSDN licenses and Azure credits.
So for Azure we can use our existing MS accounts and just set up an Azure Pay As You Go (PAYG) subscription. This was suggested to us initially but it seems weird to have the entire companies Azure environment going through an individuals live ID. Then we saw we can sign up as an Organization now and it uses Azure AD. We have not been using Active Directory and we're not sure how much complexity this is going to add to our administration. Is there a discernible difference/benefit to going one way or the other?
Then, when we sign up our developers we can either have everyone sign up with their live ID's (we have MSDN w/ VS Premium credits for all developers) or we can set them up using Active Directory with Work Accounts. Having our credits allotted in work accounts sounds like a good way to control things at first reading, but it also seems a bit more complex. I'm wondering if there is much difference between MSDN accounts signed up w/ live IDs or AD Work Accounts. I can't find a real comparison article or pro/con type of discussion anywhere.
It sounds like you have already figured out the main differences. As an organization, I would suggest signing up for Azure as an organization. You can do that here. This is going to give you the management capabilities for resources typically needed by an organization.
Your developers can continue to use the MSDN subscriptions. As Dylan commented, these are not to be used for production environments. You should consider using these for Dev/Test environments and activating your MSDN benefits. This will save you some money. More on that here.
Visual Studio Online will work with your Work Accounts and again give you more control over managing your online resources. This link describes the sign-up process for both Microsoft Accounts and Work Accounts. And if you scroll down a bit you will find your original question specifically addressed.
Finally, you can also add your Work Account(s) to your existing MSDN subscriptions if you like. This way you (and your developers) can use the same account credentials when accessing Azure Subscriptions. Information on how to do that is available in this link.
Your Work Account subscription should be limited to personnel responsible for managing your "production" environment.
After signing up for Azure as an Organization, you can add users to the directory as described here. You can also add "external" users using their existing Microsoft Accounts. It's just a few dialogs to add a user.