I deleted a set of groups today that turns out people needed. HELP!
The ones I deleted manually I can recover with the
get-AzureADMSDeletedGroup cmdlet as the documentation says.
But I deleted a lot of groups using the Remove-DistributionGroup cmdlet and these do not appear in the above DeletedGroup cmdlet. How can I get these back?
Looks like cmdlet deletions can't be restored. :-(
https://answers.microsoft.com/en-us/msteams/forum/all/how-to-restore-a-group-deleted-with-remove/bea893c4-532d-4922-b4d0-5dc909eda9c9?rtAction=1659488104148
Related
Azure storage tables implement Etag which I would like to use to confirm that I am updating the latest entry to avoid overwriting my changes when there are multiple updates happening. However, I cannot figure out how can I use this with the AzTable PS module as it seems to just overwrite and does not care about the Etag. Can I somehow make AzTable module to use Etag or any other way to achieve this in Powershell?
I am currently following https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-how-to-use-powershell and bumped into this problem.
I have found out that the easiest way to achieve this is to change the 'InsertOrMerge' to 'Merge' in the 'Update-AzTableRow'-function https://github.com/paulomarquesc/AzureRmStorageTable/blob/master/AzureRmStorageTableCoreHelper.psm1#L696
What happened to the
'Microsoft.RecoveryServices/Vaults/backupJobsExport/operationResults/read'
'Microsoft.RecoveryServices/Vaults/backupManagementMetaData/read'
operations in Azure? They exist in this documentation...
https://learn.microsoft.com/en-us/rest/api/recoveryservices/operations%20vaults/list
but not in this documentation...
https://learn.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations
and I cannot find them in the output of the Get-AzureRmProviderOperation powershell command.
Were the operations renamed or have the services they grant access to no longer support those operations?
Those 2 operations were definitely removed as part of following commit on github.
I will try to find out about 2nd part of this question ..ie. what is the replacement or change
https://github.com/MicrosoftDocs/azure-docs/commit/49a405a66cd91e29f9f07dfe0e057d9fdee7ac50?diff=split
Both these operations are not required for RBAC to run and hence they were removed from the ‘resource-provider-operations’ URL. The Microsoft engineer said that they will be removed from the other document as well to keep the documentation consistent.
I had an Azure Log Analytics Worspace with two Solutions and I deleted the Workspace without deleting the Solutions. Now when I try to delete the Solutions I'm getting an Unknown error from the portal.
I've tried deleting the resource using PowerShell but it still doesn't work and I dont't get a specific error also.
Well... It seems that after some time after the Workspace is deleted the Solutions are deleted automatically, but it takes some time and is somewhat confusing. So keeping this question and answer here to save future time of others experiencing the same problem ;-)
I have a standard Azure build -- one web role, one worker role. After the latest merge, it has decided that the roles are invalid. When I double click on the web role or worker role, or when I right click and choose "Properties", I get a grey screen saying "Invalid service definition or service configuration. Please see the Error List for more details". However, there is nothing at all in the Error List.
I have cross-compared the Settings elements and tried commenting out sections of the csdef and cscfg files, but nothing seems to bring the roles back to life. I have wasted half a day on this already. My question is not so much "What is wrong" -- more like, how on Earth are you supposed to find out what the error is when no information is given and successive blanking out of code draws a comprehensive blank?
I've run across this a couple of times (VS 2015 Enterprise). Simply closing and re-opening the solution resolved the issue.
In this case, nothing was wrong with the csdef and cscfg files. It was the way the wadcfgx files were linked to the roles.
I'm on a branch that is using Azure 2.5; the other branch is on a previous version of Azure, that uses the older version of diagnostics. By deleting the existing wadcfgx files and re-generating them, I was able to make the roles visible and editable again. Having different versions on different branches does, of course, open a very large can of worms, but we're stuck with that difficult situation for the time being.
Check if the VM Size specified in the configuration is Small or Extra Small as it doesn't support more than that on local emulator. In my case it was defaulted to Standard Size VM. I changed the size to Extra Small and it started working fine!
I just ran into this after adding a new Worker Role project to an existing cloud service with a few existing Worker Roles.
In my ServiceConfiguration.Cloud.cscfg, I had a <NetworkConfiguration> tag in between the old roles and the new role. This was the problem. I simply moved the <NetworkConfiguration> tag to the bottom as it was before (this tag is not in my ServiceConfiguration.Local.cscfg file, which might've been the problem).
Probably not the most common cause of this problem, but figured I'd post on the off chance someone has similar settings.
I've been working with the Azure Powershell scripts from Microsoft over the last new days and am becoming frustrated with how often they seem to fail silently or give very misleading error messages. I have tried using the -verbose option, but this isn't very verbose.
Does any have any tips of things I can try to beef up the feedback when something goes wrong?
For example: Save-AzureServiceProjectPackage is reporting that the cloud_package.cspkg is created but no file is created on disk. If I delete my node_modules folder it works correctly and reports the same thing!
I've raised this direct with the team, but it appears the problem is with cspack.exe which the powershell calls: https://github.com/Azure/azure-sdk-tools/issues/2689
I had similar problems.
What didn't work: to install the latest SDK for Azure (Libraries for .NET and Azure Powershell)
What did work: to shorten the longest directory path.
For instance, in your deepest subdirectories, you delete everything not needed. Or move your $DEV_ROOT directory to the drive's top level. It's not a nice solution though.