profile
viewpoint
Amit Sengupta amitse Microsoft Hyderabad Let's try something new.

amitse/3Coffee 0

A simple Java-based 2D game engine that was written during boring lectures.

amitse/alm 0

:rose: A :cloud: ready IDE just for TypeScript :heart:

amitse/AndroidMetronome 0

Just another android metronome!

amitse/AndroidProject0 0

Udacity nanodegree project 0

amitse/angular-activity-monitor 0

An Angular 1.x service that tracks users' DOM activity

amitse/angular-styleguide 0

Angular Style Guide: A starting point for Angular development teams to provide consistency through good practices.

issue commentAzure/azure-powershell

Breaking change New-AzSubscription has been removed in version 5.0.0

We see the exact same issue here.

New-AzSubscription works but when shifting to New-AzSubscriptionAlias we get the unauthorized exception using the same SPN/App Registration as before. So maybe something changed also on the permissions side for the user?

michaelpace-tnt

comment created time in 6 minutes

issue openedAzure/azure-powershell

Creating a Dev/Test subscription with New-AzSubscription with Operation: Badrequest

Run this from an ADO pipeline on our release server: New-AzSubscription -OfferType MS-AZR-0148P -Name $Sub.SubscriptionName -EnrollmentAccountObjectId $EnrollAccObjId -OwnerObjectId $OwnerObjId

That give this error: 2020-11-27T12:12:45.1499038Z ##[error]Operation returned an invalid status code 'BadRequest' 2020-11-27T12:12:45.3506619Z ##[error]PowerShell exited with code '1'.

Normal enteprise agreemens with offertype MS-AZR-0017P don't fail and succeeded in creating

created time in 2 hours

Pull request review commentAzure/azure-powershell

Add flexible commands to MySql modules

+---+external help file:+Module Name: Az.MySql+online version: https://docs.microsoft.com/en-us/powershell/module/az.mysql/update-azmysqlflexibleserverfirewallrule+schema: 2.0.0+---++# Update-AzMySqlFlexibleServerFirewallRule++## SYNOPSIS+Creates a new firewall rule or updates an existing firewall rule.++## SYNTAX++### UpdateExpanded (Default)+```+Update-AzMySqlFlexibleServerFirewallRule -Name <String> -ResourceGroupName <String> -ServerName <String>+ -EndIPAddress <String> -StartIPAddress <String> [-SubscriptionId <String>] [-DefaultProfile <PSObject>]+ [-AsJob] [-NoWait] [-Confirm] [-WhatIf] [<CommonParameters>]+```++### ClientIPAddress+```+Update-AzMySqlFlexibleServerFirewallRule -Name <String> -ResourceGroupName <String> -ServerName <String>+ -ClientIPAddress <String> [-SubscriptionId <String>] [-DefaultProfile <PSObject>] [-AsJob] [-NoWait]+ [-Confirm] [-WhatIf] [<CommonParameters>]+```++### ClientIPAddressViaIdentity+```+Update-AzMySqlFlexibleServerFirewallRule -InputObject <IMySqlIdentity> -ClientIPAddress <String>+ [-DefaultProfile <PSObject>] [-AsJob] [-NoWait] [-Confirm] [-WhatIf] [<CommonParameters>]+```++### UpdateViaIdentityExpanded+```+Update-AzMySqlFlexibleServerFirewallRule -InputObject <IMySqlIdentity> -EndIPAddress <String>+ -StartIPAddress <String> [-DefaultProfile <PSObject>] [-AsJob] [-NoWait] [-Confirm] [-WhatIf]+ [<CommonParameters>]+```++## DESCRIPTION+Creates a new firewall rule or updates an existing firewall rule.++## EXAMPLES++### -------------------------- EXAMPLE 1 --------------------------+```powershell+Update-AzMySqlFlexibleServerFirewallRule -Name rule -ResourceGroupName PowershellMySqlTest -ServerName mysql-test -EndIPAddress 0.0.0.3 -StartIPAddress 0.0.0.2+```

The example files I wrote includes the output in the quotation marks, but the autogenerated docs file don't include it. This was the autogeneration problem I was asking you about.. Not just flexible server documents but also single server documents. Do you think the powershell version would be the problem? I'm using PSVersion 5.1.19041.610 and pwsh 7.0.3..

The commit 19ad16d4ec584fe5791b06b57deb416bcc56dcbe include the codes I generated using your config. I am using the powershell core 7.0.3 but cannot reproduce your issue.

DaeunYim

comment created time in 6 hours

issue commentAzure/azure-powershell

[1.4.0] Start-AzAutomationRunbook is converting the json parameters to clixml

we are seeing the issue due to this commit : https://github.com/Azure/azure-powershell/commit/9562911d02e19978cb668f1e3ea0f55cd16862b4#diff-415dc886667885776ccc3a94b73722653b94d33be77a8421620c8522e1f20e62

Have looped in the Powershell team to look into this.

sridharktm

comment created time in 7 hours

created tagAzure/azure-powershell

tagAz.Migrate-v0.1.1

Microsoft Azure PowerShell

created time in 7 hours

release Azure/azure-powershell

Az.Migrate-v0.1.1

released time in 7 hours

PR opened Azure/azure-powershell

[KeyVault] Redesign HSM cmdlets

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

<!-- Please add a brief description of the changes made in this PR -->

According to our discussion with KeyVault team, here's the summary of the changes:

  1. Management plane
    • Rename, add "KeyVault" prefix
    • Old: New-AzManagedHsm
    • New: New-AzKeyVaultManagedHsm
  2. Key operations
    • Merge with existing "KeyVaultKey" cmdlets
    • Make -VaultName and -HsmName exclusive for different scenarios
    • Old: Add-AzKeyVaultKey and Add-AzManagedHsmKey
    • New: Merge both into Add-AzKeyVaultKey
  3. RBAC
    • Rename, use "KeyVault" as prefix
    • Old: Get-AzManagedHsmRoleDefinition
    • New: Get-AzKeyVaultRoleDefinition
  4. Full backup & restore
    • Rename, use "KeyVault" as prefix
    • Old: Backup-AzManagedHsm
    • New: Backup-AzKeyVault
  5. Security domain
    • Rename, use "KeyVault" as prefix
    • Use verb Export and Import
    • Old: Backup-AzManagedHsmSecurityDomain and Restore-AzManagedHsmSecurityDomain
    • New: Export-AzKeyVaultSecurityDomain and Import-AzKeyVaultSecurityDomain

Checklist

  • [x] I have read the Submitting Changes section of CONTRIBUTING.md
  • [x] The title of the PR is clear and informative
  • [x] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [ ] The PR does not introduce breaking changes
  • [x] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • [ ] the markdown help files have been regenerated using the commands listed here
+1486 -3666

0 comment

73 changed files

pr created time in 8 hours

PR closed Azure/azure-powershell

[KeyVault] Redesign HSM related cmdlets

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

<!-- Please add a brief description of the changes made in this PR -->

According to our discussion with KeyVault team, here's the summary of the changes:

  1. Management plane
    • Rename, add "KeyVault" prefix
    • Old: New-AzManagedHsm
    • New: New-AzKeyVaultManagedHsm
  2. Key operations
    • Merge with existing "KeyVaultKey" cmdlets
    • Make -VaultName and -HsmName exclusive for different scenarios
    • Old: Add-AzKeyVaultKey and Add-AzManagedHsmKey
    • New: Merge both into Add-AzKeyVaultKey
  3. RBAC
    • Rename, use "KeyVault" as prefix
    • Old: Get-AzManagedHsmRoleDefinition
    • New: Get-AzKeyVaultRoleDefinition
  4. Full backup & restore
    • Rename, use "KeyVault" as prefix
    • Old: Backup-AzManagedHsm
    • New: Backup-AzKeyVault
  5. Security domain
    • Rename, use "KeyVault" as prefix
    • Use verb Export and Import
    • Old: Backup-AzManagedHsmSecurityDomain and Restore-AzManagedHsmSecurityDomain
    • New: Export-AzKeyVaultSecurityDomain and Import-AzKeyVaultSecurityDomain

Checklist

  • [x] I have read the Submitting Changes section of CONTRIBUTING.md
  • [x] The title of the PR is clear and informative
  • [x] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [ ] The PR does not introduce breaking changes
  • [x] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • [ ] the markdown help files have been regenerated using the commands listed here
+1464 -2567

0 comment

64 changed files

isra-fel

pr closed time in 8 hours

PR opened Azure/azure-powershell

[KeyVault] Redesign HSM related cmdlets

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

<!-- Please add a brief description of the changes made in this PR -->

According to our discussion with KeyVault team, here's the summary of the changes:

  1. Management plane
    • Rename, add "KeyVault" prefix
    • Old: New-AzManagedHsm
    • New: New-AzKeyVaultManagedHsm
  2. Key operations
    • Merge with existing "KeyVaultKey" cmdlets
    • Make -VaultName and -HsmName exclusive for different scenarios
    • Old: Add-AzKeyVaultKey and Add-AzManagedHsmKey
    • New: Merge both into Add-AzKeyVaultKey
  3. RBAC
    • Rename, use "KeyVault" as prefix
    • Old: Get-AzManagedHsmRoleDefinition
    • New: Get-AzKeyVaultRoleDefinition
  4. Full backup & restore
    • Rename, use "KeyVault" as prefix
    • Old: Backup-AzManagedHsm
    • New: Backup-AzKeyVault
  5. Security domain
    • Rename, use "KeyVault" as prefix
    • Use verb Export and Import
    • Old: Backup-AzManagedHsmSecurityDomain and Restore-AzManagedHsmSecurityDomain
    • New: Export-AzKeyVaultSecurityDomain and Import-AzKeyVaultSecurityDomain

Checklist

  • [x] I have read the Submitting Changes section of CONTRIBUTING.md
  • [x] The title of the PR is clear and informative
  • [x] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [ ] The PR does not introduce breaking changes
  • [x] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • [ ] the markdown help files have been regenerated using the commands listed here
+1464 -2567

0 comment

64 changed files

pr created time in 8 hours

push eventAzure/azure-powershell

Yeming Liu

commit sha 1fda6ae4550587b55a84ab9b7b34835a81b1e650

misc changes

view details

push time in 8 hours

Pull request review commentAzure/azure-powershell

[Resources] Fix issue preventing deployment of Template Specs located outside of the current subscription context

 public void CreatesNewPSResourceGroupDeploymentWithUserTemplateEmptyRollback()              commandRuntimeMock.Verify(f => f.WriteObject(expected), Times.Once());         }++        /// <summary>+        /// When deployments are created using a template spec, the dynamic parameters are+        /// resolved by reading the parameters from the template spec version's template body. +        /// Previously a bug was present that prevented successful dynamic parameter resolution+        /// if the template spec existed in a subscription outside the current subscription +        /// context. This test validates dynamic parameter resolution works for deployments using+        /// cross-subscription template specs.+        /// </summary>++        [Fact]+        [Trait(Category.AcceptanceType, Category.CheckIn)]+        public void ResolvesDynamicParametersWithCrossSubTemplateSpec()+        {+            const string templateSpecSubscriptionId = "10000000-0000-0000-0000-000000000000";+            const string templateSpecRGName = "someRG";+            const string templateSpecName = "myTemplateSpec";+            const string templateSpecVersion = "v1";++            string templateSpecId = $"/subscriptions/{templateSpecSubscriptionId}/" ++                $"resourceGroups/{templateSpecRGName}/providers/Microsoft.Resources/" ++                $"templateSpecs/{templateSpecName }/versions/{templateSpecVersion}";++            var templateContentForTest = File.ReadAllText(templateFile);

The path is invalid in linux and mac.

stuartko

comment created time in 8 hours

pull request commentAzure/azure-powershell

[Resources] Fix issue preventing deployment of Template Specs located outside of the current subscription context

@msJinLei: It was more involved than anticipated due to some shell-only assumptions in the original cmdlet implementation, but I've now completed adding a unit test to cover the missing coverage for the bug being fixed.

Can you review/approve?

Great!

There's a failed test case in mac and linux

2020-11-23T09:51:24.3167640Z   [xUnit.net 00:02:05.19]     Microsoft.Azure.Commands.Resources.Test.NewAzureResourceGroupDeploymentCommandTests.ResolvesDynamicParametersWithCrossSubTemplateSpec [FAIL]
2020-11-23T09:51:24.3353190Z     X Microsoft.Azure.Commands.Resources.Test.NewAzureResourceGroupDeploymentCommandTests.ResolvesDynamicParametersWithCrossSubTemplateSpec [9ms]
2020-11-23T09:51:24.3361432Z EXEC : error Message:  [/home/vsts/work/1/s/build.proj]
2020-11-23T09:51:24.3363762Z      System.IO.FileNotFoundException : Could not find file '/home/vsts/work/1/s/src/Resources/Resources.Test/bin/Debug/netcoreapp2.1/Resources\sampleTemplateFile.json'.
2020-11-23T09:51:24.3364657Z     Stack Trace:
2020-11-23T09:51:24.3365336Z        at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
2020-11-23T09:51:24.3366123Z      at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
2020-11-23T09:51:24.3366963Z      at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
2020-11-23T09:51:24.3367794Z      at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)
2020-11-23T09:51:24.3368541Z      at System.IO.File.InternalReadAllText(String path, Encoding encoding)
2020-11-23T09:51:24.3369159Z      at System.IO.File.ReadAllText(String path)
stuartko

comment created time in 8 hours

PR closed Azure/azure-powershell

Reviewers
Fix small issues of MoveFromGeneration2Master.ps1

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

<!-- Please add a brief description of the changes made in this PR -->

Checklist

  • [ ] I have read the Submitting Changes section of CONTRIBUTING.md
  • [ ] The title of the PR is clear and informative
  • [ ] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [ ] The PR does not introduce breaking changes
  • [ ] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • [ ] the markdown help files have been regenerated using the commands listed here
+4 -2

0 comment

1 changed file

msJinLei

pr closed time in 8 hours

push eventAzure/azure-powershell

Yunchi Wang

commit sha 41897b2208e11d55c9e9c791cba61d0c2e4d4f8b

Fix the issue of generating generate-info.json (#13473) Co-authored-by: wyunchi-ms <yunwang@microsoft.com>

view details

push time in 8 hours

PR merged Azure/azure-powershell

[Tool]Fix the issue of generating generate-info.json needs-review

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

<!-- Please add a brief description of the changes made in this PR -->

Checklist

  • [x] I have read the Submitting Changes section of CONTRIBUTING.md
  • [x] The title of the PR is clear and informative
  • [x] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [x] The PR does not introduce breaking changes
  • [x] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • [ ] the markdown help files have been regenerated using the commands listed here
+24 -10

4 comments

1 changed file

wyunchi-ms

pr closed time in 8 hours

Pull request review commentAzure/azure-powershell

[MONITOR] Data Collection Rules 2019-11-01-preview - New Cmdlets

   </PropertyGroup>    <ItemGroup>-    <PackageReference Include="Microsoft.Azure.Management.Monitor" Version="0.25.2-preview" />

Please also update the Monitor sdk version in other modules' test project. Or the their tests will fail, which block the PR.

herreraj-ms

comment created time in 8 hours

Pull request review commentAzure/azure-powershell

[MONITOR] Data Collection Rules 2019-11-01-preview - New Cmdlets

 # RootModule = ''  # Version number of this module.-ModuleVersion = '2.2.0'+ModuleVersion = '2.3.0'

Our team is responsible for upgrading the module version, please undo the update

herreraj-ms

comment created time in 8 hours

Pull request review commentAzure/azure-powershell

[MONITOR] Data Collection Rules 2019-11-01-preview - New Cmdlets

  ## Upcoming Release +## Version 2.3.0

Please remove the line and put the description item under upcoming release

herreraj-ms

comment created time in 8 hours

push eventAzure/azure-powershell

zesluo

commit sha 09627e4ae587e3494eef294f4e349ffb30762bec

Remove-AzSynapseSqlPoolRestorePoint (#13412) * Remove-AzSynapseSqlPoolRestorePoint * add wsname sqlpoolname * refine restorepoint and deleteoperation * refine restore point and resource id * add help and test * refine restorepointcreatationdate * refine and simpify codes * refine test * update session records for testsynapsesqlpool * Move RemoveAzureSynapseSqlPoolRestorePoint.cs and update changelog entry * Use local resource id Co-authored-by: Dongwei Wang <dongwwa@microsoft.com>

view details

push time in 8 hours

PR merged Azure/azure-powershell

Remove-AzSynapseSqlPoolRestorePoint needs-review

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

This change add some SQL pool related cmdlets, and change some exist cmdlets to keep align with SQL. Here is the commandlet review PR:Azure/azure-powershell-cmdlet-review-pr#783

Checklist

  • [ ] I have read the Submitting Changes section of CONTRIBUTING.md
  • [ ] The title of the PR is clear and informative
  • [ ] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [ ] The PR does not introduce breaking changes
  • [ ] If applicable, the changes made in the PR have proper test coverage
  • [ ] For public API changes to cmdlets:
    • [ ] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • [ ] the markdown help files have been regenerated using the commands listed here
+2790 -1639

2 comments

12 changed files

zesluo

pr closed time in 8 hours

delete branch Azure/azure-powershell

delete branch : isra-fel-patch-1

delete time in 8 hours

delete branch Azure/azure-powershell

delete branch : yeming/stackhci

delete time in 8 hours

create barnchAzure/azure-powershell

branch : yeming/hsm-rename

created branch time in 8 hours

delete branch Azure/azure-powershell

delete branch : merge-hsm

delete time in 8 hours

create barnchAzure/azure-powershell

branch : merge-hsm

created branch time in 8 hours

issue commentAzure/azure-powershell

Breaking change New-AzSubscription has been removed in version 5.0.0

According to the documentation here and here, we just need to create a Service Principal and make that SP owner on the Enrollment Account.

Then, we need to log in as the service account and run New-AzSubscriptionAlias, exactly as we did with New-AzSubscription.

We actually were able to create new subscriptions with New-AzSubscription, but that is not the case with New-AzSubscriptionAlias. The cmdlet insists, that my SP is unauthorzed:

New-AzSubscriptionAlias: Operation returned an invalid status code 'Unauthorized'

According to the Debug log, the token gets created, and the API request to https://management.azure.com/providers/Microsoft.Subscription/aliases returns

Body:
{
  "error": {
    "code": "UserNotAuthorized",
    "message": "User is not authorized to create subscriptions on this enrollment account"
  },
  "code": "UserNotAuthorized",
  "message": "User is not authorized to create subscriptions on this enrollment account"
}
michaelpace-tnt

comment created time in 8 hours

push eventAzure/azure-powershell

bradrich-msft

commit sha 8c640a9f9c46f13847c1838b261f5eb98ac88201

Add database readscale related properties support (#13549) * rename db property and update tests * add secondaryType property * Update help files * update change log * Add back ReadReplicaCount * Add back ReadReplicaCount to the model * Make ReadReplicaCount an alias * Add ReadReplicaCount back to model

view details

push time in 9 hours

PR merged Azure/azure-powershell

Add database readscale related properties support Waiting for CI :shipit:

<!-- DO NOT DELETE THIS TEMPLATE -->

Description

  • Added SecondaryType to the following:
    • New-AzSqlDatabase
    • Set-AzSqlDatabase
    • New-AzSqlDatabaseSecondary
  • Added HighAvailabilityReplicaCount to the following:
    • New-AzSqlDatabase
    • Set-AzSqlDatabase
  • Removed ReadReplicaCount from the following:
    • New-AzSqlDatabase
    • Set-AzSqlDatabase

Checklist

  • [x] I have read the Submitting Changes section of CONTRIBUTING.md
  • [x] The title of the PR is clear and informative
  • [x] The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • [x] The PR does not introduce breaking changes
  • [x] If applicable, the changes made in the PR have proper test coverage
  • [] For public API changes to cmdlets:
    • [] a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • No new cmdlets added
    • [x] the markdown help files have been regenerated using the commands listed here
+394483 -217341

5 comments

149 changed files

bradrich-msft

pr closed time in 9 hours

issue closedAzure/azure-powershell

[MySql] Please use PtrToStringBSTR instead of PtrToStringAuto for secure string decrytion

Description

The issue happens in PowerShell 7.* in Linux/MacOS. The root cause is there is breaking change for the API PtrToStringAuto. To workaround the issue, please follow the sample below to decrpyt secure string.

$psTxt = . "$PSScriptRoot/../utils/Unprotect-SecureString.ps1" $PSBoundParameters['Password']

Source code of Unprotect-SecureSting.ps1

#This script converts securestring to plaintext

param(
    [Parameter(Mandatory, ValueFromPipeline)]
    [System.Security.SecureString]
    ${SecureString}
)

$ssPtr = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($SecureString)
try {
    $plaintext = [System.Runtime.InteropServices.Marshal]::PtrToStringBSTR($ssPtr)
} finally {
    [System.Runtime.InteropServices.Marshal]::ZeroFreeBSTR($ssPtr)
}

return $plaintext

https://github.com/Azure/azure-powershell/pull/12842/files

closed time in 9 hours

dolauli

issue commentAzure/azure-powershell

Update-ASRRecoveryPlan breaks existing pre/post actions

This issue has been fixed in our latest release.

sean-nixon

comment created time in 9 hours

more