Skip to content

Commit d7c1d02

Browse files
committed
adding link
1 parent dac4231 commit d7c1d02

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/search/service-configure-firewall.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ ms.date: 10/19/2021
1313

1414
# Configure an IP firewall for Azure Cognitive Search
1515

16-
Azure Cognitive Search supports IP rules for inbound access through a firewall, similar to the IP rules you'll find in an Azure virtual network security group. By leveraging IP rules, you can restrict search service access to an approved set of machines and cloud services. Access to data stored in your search service from these approved sets of machines and services will still require the caller to present a valid authorization token.
16+
Azure Cognitive Search supports IP rules for inbound access through a firewall, similar to the IP rules you'll find in an Azure virtual network security group. By leveraging IP rules, you can restrict search service access to an approved set of machines and cloud services. Access to data stored in your search service from the approved sets of machines and services will still require the caller to present a valid authorization token.
1717

18-
You can set IP rules in the Azure portal, as described in this article. Alternatively, you can use the [Management REST API version 2020-03-13](/rest/api/searchmanagement/), [Azure PowerShell](/powershell/module/az.search), or [Azure CLI](/cli/azure/search).
18+
You can set IP rules in the Azure portal, as described in this article, on search services provisioned at the Basic tier and above. Alternatively, you can use the [Management REST API version 2020-03-13](/rest/api/searchmanagement/), [Azure PowerShell](/powershell/module/az.search), or [Azure CLI](/cli/azure/search).
1919

2020
<a id="configure-ip-policy"></a>
2121

@@ -37,12 +37,12 @@ To retain service administration through the portal, select the "Allow access" o
3737

3838
## Allow access from your client
3939

40-
Client applications that push indexing and query requests to the search service must be represented in an IP range. On Azure, you can generally determine the IP address by pinging the FQDN of a service (for example, `ping <your-search-service-name>.search.windows.net` will return the IP address of search service).
40+
Client applications that push indexing and query requests to the search service must be represented in an IP range. On Azure, you can generally determine the IP address by pinging the FQDN of a service (for example, `ping <your-search-service-name>.search.windows.net` will return the IP address of a search service).
4141

42-
Providing IP addresses for clients ensures that the request is not rejected outright. For access to content and operations, authorization is also necessary. Use one of the following methodologies:
42+
Providing IP addresses for clients ensures that the request is not rejected outright, but for successful access to content and operations, authorization is also necessary. Use one of the following methodologies to authenticate your request:
4343

4444
+ [Key-based authentication](search-security-api-keys.md), where an admin or query API key is provided on the request
45-
+ [Role-based authorization](search-security-rbac.md), where the caller is a member of a security role on a search service.
45+
+ [Role-based authorization](search-security-rbac.md), where the caller is a member of a security role on a search service, and the [registered app presents an OAuth token](search-howto-aad.md) from Azure Active Directory.
4646

4747
### Rejected requests
4848

0 commit comments

Comments
 (0)