You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Power supply, 110-220 VAC to 12 VDC, 100 W, IP 67, Industrial temp | PS100-12-IP67 | 1 |
52
52
53
-
## Heptagon YB3x software setup
53
+
## Heptagon Systems YB3x software setup
54
54
55
-
This procedure describes how to install Defender for IoT software on the Heptagon YB3x. The installation process takes about 20 minutes. After the installation, the system restarts several times.
55
+
This procedure describes how to install Defender for IoT software on the Heptagon Systems YB3x. The installation process takes about 20 minutes. After the installation, the system restarts several times.
Copy file name to clipboardExpand all lines: articles/site-recovery/replication-appliance-support-matrix.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Support requirements for Azure Site Recovery replication appliance
3
3
description: This article describes support and requirements when deploying the replication appliance for VMware disaster recovery to Azure with Azure Site Recovery - Modernized
4
4
ms.service: azure-site-recovery
5
5
ms.topic: faq
6
-
ms.date: 04/23/2025
6
+
ms.date: 04/29/2025
7
7
ms.author: ankitadutta
8
8
author: ankitaduttaMSFT
9
9
---
@@ -37,7 +37,7 @@ Number of disks | 2, including the OS disk - 80 GB and a data disk - 620 GB
37
37
38
38
**Component** | **Requirement**
39
39
--- | ---
40
-
Operating system | Windows Server 2022
40
+
Operating system | Windows Server 2022 <br><br> **Note**: <br> - Windows Server 2019 appliances will continue to receive software updates. <br> - Upgrading OS on existing Windows server 2019 appliances to Windows Server 2022 is not supported.
41
41
Operating system locale | English (en-*)
42
42
Windows Server roles | Don't enable these roles: <br> - Active Directory Domain Services <br>- Internet Information Services <br> - Hyper-V
43
43
Group policies | Don't enable these group policies: <br> - Prevent access to the command prompt. <br> - Prevent access to registry editing tools. <br> - Trust logic for file attachments. <br> - Turn on Script Execution. <br> [Learn more](/previous-versions/windows/it-pro/windows-7/gg176671(v=ws.10))
@@ -53,6 +53,7 @@ FIPS (Federal Information Processing Standards) | Don't enable FIPS mode|
53
53
|NIC type | VMXNET3 (if the appliance is a VMware VM)|
54
54
|NAT | Supported |
55
55
56
+
56
57
>[!NOTE]
57
58
> To support communication between source machines and replication appliance using multiple subnets, you should select FQDN as the mode of connectivity during the appliance setup. This will allow source machines to use FQDN, along with a list of IP addresses, to communicate with replication appliance.
title: Azure Front Door Web Application Firewall CAPTCHA (preview)
3
+
description: Learn about the CAPTCHA feature in Azure Front Door Web Application Firewall (WAF) and how it helps protect your web applications from automated attacks.
4
+
author: halkazwini
5
+
ms.author: halkazwini
6
+
ms.service: azure-web-application-firewall
7
+
ms.topic: concept-article
8
+
ms.date: 04/29/2025
9
+
10
+
---
11
+
12
+
# Azure Front Door Web Application Firewall CAPTCHA (preview)
13
+
14
+
> [!IMPORTANT]
15
+
> Web Application Firewall CAPTCHA on Azure Frond Door is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
16
+
17
+
Azure Web Application Firewall (WAF) offers a CAPTCHA feature designed to differentiate human users from automated bots. This interactive challenge requires suspected traffic to complete a CAPTCHA test, blocking malicious automated requests while allowing legitimate users to proceed seamlessly. As a result, WAF helps protect applications from bot-driven attacks, including brute-force attempts and account takeover risks.
18
+
19
+
CAPTCHA on Azure WAF is useful in login and sign-up flows where human authentication is crucial to protect sensitive user data. It acts as a strong defense against various automated threats, preventing bots from accessing critical website elements like login pages and forms, and reducing spam by ensuring only real users can submit comments, register accounts, or complete transactions.
20
+
21
+
Incorporating CAPTCHA into Azure WAF not only enhances security but also minimizes friction for legitimate users. This balance strengthens the overall protection of web applications against sophisticated automated threats.
22
+
23
+
## How it works
24
+
25
+
When the CAPTCHA challenge is active on Azure WAF, any client's HTTP(s) request matches a specific rule prompts an interactive Microsoft CAPTCHA page. This challenge requires user participation to verify they're human before their request is validated by Azure WAF. Upon successful completion, WAF recognizes the request as originating from a legitimate user, and proceeds with standard rule processing. Requests that fail to complete the challenge are blocked, thus preventing automated bots from accessing protected resources.
26
+
27
+
:::image type="content" source="../media/captcha-challenge/browser-captcha.png" alt-text="Screenshot of Web Application Firewall CAPTCHA in the browser.":::
28
+
29
+
30
+
## Expiration
31
+
32
+
The WAF **Policy settings** define the CAPTCHA challenge cookie validity lifetime in minutes, determining how long a user remains validated before facing a new challenge. Once the lifetime expires, the user must complete the CAPTCHA challenge again to verify their identity. The lifetime is configurable between 5 and 1,440 minutes, with a default setting of 30 minutes. The CAPTCHA challenge cookie name is `afd_azwaf_captcha` on Azure Front Door.
33
+
34
+
> [!NOTE]
35
+
> The CAPTCHA challenge expiration cookie is injected into the user’s browser after successfully completing the challenge.
36
+
37
+
## Limitations
38
+
39
+
-**Mobile Apps**: Not supported.
40
+
41
+
-**AJAX and API calls aren't supported**: CAPTCHA verification doesn't apply to AJAX and API requests.
42
+
43
+
-**POST body size restriction**: The first request that triggers a CAPTCHA challenge will be blocked if its POST body exceeds 128 KB.
44
+
45
+
-**Non-HTML embedded resources**: CAPTCHA is designed for HTML resources. Placing CAPTCHA in front of non-HTML resources, such as images, CSS, or JavaScript files, may likely result in issues with content loading and rendering.
46
+
47
+
-**Browser compatibility**: CAPTCHA isn't supported on Microsoft Internet Explorer. It's compatible with the latest versions of Microsoft Edge, Chrome, Firefox, and Safari.
0 commit comments