Skip to content

Commit 425695a

Browse files
committed
Update example pics
1 parent 863f7f3 commit 425695a

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed
39.2 KB
Loading
1.69 KB
Loading

articles/orbital/prepare-network.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Steps:
2828
2929
Here is an example of a typical VNET setup with a subnet delegated to Azure Orbital Ground Station.
3030

31-
:::image type="content" source="media/azure-ground-station-subnet-example.png" alt-text="Example VNET with subnet delegated to Orbital" lightbox="media/azure-ground-station-subnet-example.png":::
31+
:::image type="content" source="media/azure-ground-station-subnet-example.png" alt-text="Screenshot of subnet configuration with Orbital delegated subnet." lightbox="media/azure-ground-station-subnet-example.png":::
3232

3333
## Setting up the contact profile
3434

@@ -58,7 +58,7 @@ When you create a contact, you can find these IPs by viewing the contact propert
5858

5959
You can use this information to set up network policies or to distinguish between simultaneous contacts to the same endpoint.
6060

61-
:::image type="content" source="media/azure-ground-station-contact-ips-example.png" alt-text="How to find connection details in the contact object" lightbox="media/azure-ground-station-contact-ips-example.png":::
61+
:::image type="content" source="media/azure-ground-station-contact-ips-example.png" alt-text="Screenshot of contact object with source and destination IPs." lightbox="media/azure-ground-station-contact-ips-example.png":::
6262

6363
> [!NOTE]
6464
> - The source and destination IPs are always taken from the subnet address range.

0 commit comments

Comments
 (0)