Skip to content

Commit 293b273

Browse files
committed
Updates
1 parent 2f8fbb4 commit 293b273

File tree

4 files changed

+1
-2
lines changed

4 files changed

+1
-2
lines changed

articles/payment-hsm/access-payshield-manager.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,6 @@ Make a note of where the private SSH key is saved, and the value for "FullyQuali
126126
To create a VM on your new subnet:
127127

128128
1. select "Virtual machines" from the "Create a Resource" screen of the Azure portal:
129-
130129
:::image type="content" source="./media/portal-create-vm-1.png" alt-text="Screenshot of the portal resource picker.":::
131130
1. On the "Basics" tab of the creation screen, select the resource group that contains your payment HSM ("myResourceGroup"):
132131
:::image type="content" source="./media/portal-create-vm-2.png" alt-text="Screenshot of the portal main VM creation screen.":::
Binary file not shown.
-414 KB
Binary file not shown.

articles/payment-hsm/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Payment HSMs are provisioned and connected directly to users' virtual network, a
2424
2525
## Why use Azure Payment HSM?
2626

27-
Momentum is building as financial institutions move some or all of their payment applications to the cloud, requiring a migration from the legacy on-premises (on-premise) applications and HSMs to a cloud-based infrastructure that isn't generally under their direct control. Often it means a subscription service rather than perpetual ownership of physical equipment and software. Corporate initiatives for efficiency and a scaled-down physical presence are the drivers for this shift. Conversely, with cloud-native organizations, the adoption of cloud-first without any on-premises presence is their fundamental business model. Whatever the reason, end users of a cloud-based payment infrastructure expect reduced IT complexity, streamlined security compliance, and flexibility to scale their solution seamlessly as their business grows.
27+
Momentum is building as financial institutions move some or all of their payment applications to the cloud, requiring a migration from the legacy on-premises applications and HSMs to a cloud-based infrastructure that isn't generally under their direct control. Often it means a subscription service rather than perpetual ownership of physical equipment and software. Corporate initiatives for efficiency and a scaled-down physical presence are the drivers for this shift. Conversely, with cloud-native organizations, the adoption of cloud-first without any on-premises presence is their fundamental business model. Whatever the reason, end users of a cloud-based payment infrastructure expect reduced IT complexity, streamlined security compliance, and flexibility to scale their solution seamlessly as their business grows.
2828

2929
The cloud offers significant benefits, but challenges when migrating a legacy on-premises payment application (involving payment HSMs) to the cloud must be addressed:
3030

0 commit comments

Comments
 (0)