Skip to content

Commit 161cbda

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mdb-troubleshooting-appendix
2 parents 545a64e + 7c68034 commit 161cbda

File tree

167 files changed

+1470
-896
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

167 files changed

+1470
-896
lines changed

articles/automation/change-tracking/overview-monitoring-agent.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Automation Change Tracking and Inventory overview using Azure Monit
33
description: This article describes the Change Tracking and Inventory feature using Azure monitoring agent, which helps you identify software and Microsoft service changes in your environment.
44
services: automation
55
ms.subservice: change-inventory-management
6-
ms.date: 11/15/2024
6+
ms.date: 12/09/2024
77
ms.topic: overview
88
ms.service: azure-automation
99
---
@@ -21,6 +21,20 @@ This article explains on the latest version of change tracking support using Azu
2121
> - [FIM with Change Tracking and Inventory using AMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-ama).
2222
> - [FIM with Change Tracking and Inventory using MMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-mma).
2323
24+
## What is Change Tracking & Inventory
25+
26+
Azure Change Tracking & Inventory service enhances the auditing and governance for in-guest operations by monitoring changes and providing detailed inventory logs for servers across Azure, on-premises, and other cloud environments.
27+
28+
1. **Change Tracking**
29+
30+
a. Monitors changes, including modifications to files, registry keys, software installations, and Windows services or Linux daemons.</br>
31+
b. Provides detailed logs of what and when the changes were made, who made them, enabling you to quickly detect configuration drifts or unauthorized changes.
32+
33+
1. **Inventory**
34+
35+
a. Collects and maintains an updated list of installed software, operating system details, and other server configurations in linked LA workspace </br>
36+
b. Helps create an overview of system assets, which is useful for compliance, audits, and proactive maintenance.
37+
2438
## Support matrix
2539

2640
|**Component**| **Applies to**|

articles/azure-cache-for-redis/cache-how-to-premium-vnet.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,10 @@ ms.date: 08/29/2023
2727
- failure of replica node to replicate data from primary node
2828
- potential data loss
2929
- failure of management operations like scaling
30+
- intermittent or complete SSL/TLS failures
3031
- in the most severe scenarios, loss of availability
3132
- VNet injected caches are only available for Premium-tier Azure Cache for Redis, not other tiers.
32-
- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
33+
- When using a VNet injected cache, you must change your VNet to cache dependencies such as Certificate Revocation Lists/Public Key Instructure, Azure Key Vault, Azure Storage, Azure Monitor, and more.
3334
- You can't inject an existing Azure Cache for Redis instance into a Virtual Network. You must select this option when you _create_ the cache.
3435

3536
## Set up virtual network support
@@ -166,9 +167,9 @@ There are network connectivity requirements for Azure Cache for Redis that might
166167

167168
- Outbound network connectivity to Azure Key Vault endpoints worldwide. Azure Key Vault endpoints resolve under the DNS domain `vault.azure.net`.
168169
- Outbound network connectivity to Azure Storage endpoints worldwide. Endpoints located in the same region as the Azure Cache for Redis instance and storage endpoints located in _other_ Azure regions are included. Azure Storage endpoints resolve under the following DNS domains: `table.core.windows.net`, `blob.core.windows.net`, `queue.core.windows.net`, and `file.core.windows.net`.
169-
- Outbound network connectivity to `ocsp.digicert.com`, `crl4.digicert.com`, `ocsp.msocsp.com`, `mscrl.microsoft.com`, `crl3.digicert.com`, `cacerts.digicert.com`, `oneocsp.microsoft.com`, and `crl.microsoft.com`. This connectivity is needed to support TLS/SSL functionality.
170+
- Outbound network connectivity to `ocsp.digicert.com`, `crl4.digicert.com`, `ocsp.msocsp.com`, `mscrl.microsoft.com`, `crl3.digicert.com`, `cacerts.digicert.com`, `oneocsp.microsoft.com`, and `crl.microsoft.com`, `cacerts.geotrust.com`, `www.microsoft.com`, `cdp.geotrust.com`, `status.geotrust.com`. This connectivity is needed to support TLS/SSL functionality.
170171
- The DNS configuration for the virtual network must be able to resolve all of the endpoints and domains mentioned in the earlier points. These DNS requirements can be met by ensuring a valid DNS infrastructure is configured and maintained for the virtual network.
171-
- Outbound network connectivity to the following Azure Monitor endpoints, which resolve under the following DNS domains: `shoebox2-black.shoebox2.metrics.nsatc.net`, `north-prod2.prod2.metrics.nsatc.net`, `azglobal-black.azglobal.metrics.nsatc.net`, `shoebox2-red.shoebox2.metrics.nsatc.net`, `east-prod2.prod2.metrics.nsatc.net`, `azglobal-red.azglobal.metrics.nsatc.net`, `shoebox3.prod.microsoftmetrics.com`, `shoebox3-red.prod.microsoftmetrics.com`, `shoebox3-black.prod.microsoftmetrics.com`, `azredis-red.prod.microsoftmetrics.com` and `azredis-black.prod.microsoftmetrics.com`.
172+
- Outbound network connectivity to the following Azure Monitor endpoints, which resolve under the following DNS domains: `shoebox3.prod.microsoftmetrics.com`, `shoebox3-red.prod.microsoftmetrics.com`, `shoebox3-black.prod.microsoftmetrics.com`, `azredis.prod.microsoftmetrics.com`, `azredis-red.prod.microsoftmetrics.com`, and `azredis-black.prod.microsoftmetrics.com`.
172173

173174
### How can I verify that my cache is working in a virtual network?
174175

@@ -206,6 +207,8 @@ If you're unable to resolve the DNS name, some client libraries include configur
206207

207208
`10.128.2.84:6380,password=xxxxxxxxxxxxxxxxxxxx,ssl=True,abortConnect=False;sslHost=[mycachename].redis.cache.windows.net`
208209

210+
In addition, if the subnet where Azure Cache for Redis is hosted is blocking TCP outbound connections over port 80 for SSL/TLS functionality, clients might experience intermittent TLS certificate validation errors.
211+
209212
### Can I use virtual networks with a standard or basic cache?
210213

211214
Virtual networks can only be used with Premium-tier caches.

articles/azure-resource-manager/bicep/bicep-cli.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Bicep CLI commands and overview
33
description: Describes the commands that you can use in the Bicep CLI. These commands include building Azure Resource Manager templates from Bicep.
44
ms.topic: reference
55
ms.custom: devx-track-azurecli, devx-track-bicep, devx-track-arm-template
6-
ms.date: 10/30/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Bicep CLI commands
@@ -116,13 +116,13 @@ The `generate-params` command builds a parameters file from the given Bicep file
116116
az bicep generate-params --file main.bicep --output-format bicepparam --include-params all
117117
```
118118

119-
The command creates a Bicep parameters file named _main.bicepparam_. The parameter file contains all parameters in the Bicep file, whether configured with default values or not.
119+
The command creates a Bicep parameters file named _main.bicepparam_. The parameters file contains all parameters in the Bicep file, whether configured with default values or not.
120120

121121
```azurecli
122122
az bicep generate-params --file main.bicep --outfile main.parameters.json
123123
```
124124

125-
The command creates a parameter file named _main.parameters.json_. The parameter file only contains the parameters without default values configured in the Bicep file.
125+
The command creates a parameters file named _main.parameters.json_. The parameters file only contains the parameters without default values configured in the Bicep file.
126126

127127
## install
128128

articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Bicep functions - parameters file
3-
description: This article describes the Bicep functions to be used in Bicep parameter files.
3+
description: This article describes the Bicep functions to be used in Bicep parameters files.
44
ms.topic: reference
55
ms.custom: devx-track-bicep
6-
ms.date: 08/09/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Parameters file function for Bicep

articles/azure-resource-manager/bicep/bicep-functions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Bicep functions
33
description: Describes the functions to use in a Bicep file to retrieve values, work with strings and numerics, and retrieve deployment information.
44
ms.topic: reference
55
ms.custom: devx-track-bicep
6-
ms.date: 05/21/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Bicep functions
@@ -128,7 +128,7 @@ The following functions are available for working with objects. All of these fun
128128

129129
## Parameters file functions
130130

131-
The following functions are available to be used in Bicep parameter files. All of these functions are in the `sys` namespace.
131+
The following functions are available to be used in Bicep parameters files. All of these functions are in the `sys` namespace.
132132

133133
* [getSecret](./bicep-functions-parameters-file.md)
134134
* [readEnvironmentVariable](./bicep-functions-parameters-file.md)

articles/azure-resource-manager/bicep/bicep-import.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Imports in Bicep
33
description: This article describes how to import shared functionality and namespaces in Bicep.
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep
6-
ms.date: 10/23/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Imports in Bicep
@@ -80,7 +80,7 @@ output greeting string = sayHello('Bicep user')
8080
output exampleObject myImports.myObjectType = exampleObject
8181
```
8282

83-
## Import namespaces and extensions (preview)
83+
## Import namespaces and extensions (Preview)
8484

8585
> [!NOTE]
8686
> The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
@@ -112,7 +112,8 @@ For an example, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md
112112

113113
## Related content
114114

115-
- To learn about Bicep data types, see [Data types](./data-types.md).
116-
- To learn about Bicep functions, see [Bicep functions](./bicep-functions.md).
117-
- To learn how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
118-
- To go through a Kubernetes extension tutorial, see [Quickstart: Deploy Azure applications to Azure Kubernetes Services by using the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
115+
- To learn about the Bicep data types, see [Data types](./data-types.md).
116+
- To learn about the Bicep functions, see [Bicep functions](./bicep-functions.md).
117+
- To learn about how to use the Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
118+
- To go through a Kubernetes extension tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension.](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
119+
- To learn about how to use the Microsoft Graph extension, see [Bicep templates for Microsoft Graph](https://aka.ms/graphbicep).

articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ The Kubernetes extension allows you to create Kubernetes resources directly with
2424
> }
2525
>
2626
> ```
27-
>
2827
2928
## Enable the preview feature
3029
@@ -81,4 +80,5 @@ From Visual Studio Code, you can import Kubernetes manifest files to create Bice
8180

8281
## Next steps
8382

84-
- [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension)
83+
- To walk through a quickstart, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
84+
- To learn about how to use the Microsoft Graph extension, see [Bicep templates for Microsoft Graph](https://aka.ms/graphbicep).

articles/azure-resource-manager/bicep/bicep-using.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ title: Using statement
33
description: Describes how to use the using statement in Bicep.
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep
6-
ms.date: 06/28/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Using statement
1010

11-
The `using` statement in [Bicep parameter files](./parameter-files.md) ties the [Bicep parameters file](./parameter-files.md) to a [Bicep file](./file.md), an [ARM JSON template](../templates/syntax.md), or a [Bicep module](./modules.md), or a [template spec](./template-specs.md). A `using` declaration must be present in any Bicep parameters file.
11+
The `using` statement in [Bicep parameters files](./parameter-files.md) ties the [Bicep parameters file](./parameter-files.md) to a [Bicep file](./file.md), an [ARM JSON template](../templates/syntax.md), or a [Bicep module](./modules.md), or a [template spec](./template-specs.md). A `using` declaration must be present in any Bicep parameters file.
1212

1313
> [!NOTE]
1414
> The Bicep parameters file is only supported in [Bicep CLI](./install.md) version 0.18.4 or newer, [Azure CLI](/cli/azure/install-azure-cli) version 2.47.0 or newer, and [Azure PowerShell](/powershell/azure/install-azure-powershell) version 9.7.1 or newer.

articles/azure-resource-manager/bicep/data-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Data types in Bicep
33
description: This article describes the data types that are available in Bicep.
44
ms.topic: reference
55
ms.custom: devx-track-bicep
6-
ms.date: 11/12/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Data types in Bicep
@@ -111,7 +111,7 @@ When you specify integer values, don't use quotation marks.
111111
param exampleInt int = 1
112112
```
113113

114-
Bicep integers are 64-bit integers. When they're passed as inline parameters, the SDK or command-line tool you use for deployment can limit the range of values. For example, when you use PowerShell to deploy Bicep, integer types can range from -2147483648 to 2147483647. To avoid this limitation, specify large integer values in a [parameter file](parameter-files.md). Resource types apply their own limits for integer properties.
114+
Bicep integers are 64-bit integers. When they're passed as inline parameters, the SDK or command-line tool you use for deployment can limit the range of values. For example, when you use PowerShell to deploy Bicep, integer types can range from -2147483648 to 2147483647. To avoid this limitation, specify large integer values in a [parameters file](parameter-files.md). Resource types apply their own limits for integer properties.
115115

116116
Bicep supports an integer literal type that refers to a specific value that's an exact integer. In the following example, `1` is an integer literal type, and `foo` can only be assigned the value `1` and no other value.
117117

articles/azure-resource-manager/bicep/deploy-cli.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Deploy resources with Azure CLI and Bicep files | Microsoft Docs
33
description: Use Azure Resource Manager and Azure CLI to deploy resources to Azure. The resources are defined in a Bicep file.
44
ms.topic: how-to
5-
ms.date: 03/22/2024
5+
ms.date: 12/06/2024
66
ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template, devx-track-bicep
77
---
88

@@ -93,7 +93,7 @@ Currently, Azure CLI doesn't support deploying remote Bicep files. You can use [
9393

9494
## Parameters
9595

96-
To pass parameter values, you can use either inline parameters or a parameters file. The parameters file can be either a [Bicep parameters file](#bicep-parameter-files) or a [JSON parameters file](#json-parameter-files).
96+
To pass parameter values, you can use either inline parameters or a parameters file. The parameters file can be either a [Bicep parameters file](#bicep-parameters-files) or a [JSON parameters file](#json-parameters-files).
9797

9898
### Inline parameters
9999

@@ -174,11 +174,11 @@ However, if you're using Azure CLI with Windows Command Prompt (CMD) or PowerShe
174174

175175
The evaluation of parameters follows a sequential order, meaning that if a value is assigned multiple times, only the last assigned value is used. To ensure proper parameter assignment, it's advised to provide your parameters file initially and selectively override specific parameters using the _KEY=VALUE_ syntax. It's important to mention that if you're supplying a `bicepparam` parameters file, you can use this argument only once.
176176

177-
### Bicep parameter files
177+
### Bicep parameters files
178178

179-
Rather than passing parameters as inline values in your script, you might find it easier to use a parameters file, either a [Bicep parameters file](#bicep-parameter-files) or a [JSON parameters file](#json-parameter-files) that contains the parameter values. The parameters file must be a local file. External parameters files aren't supported with Azure CLI. For more information about the parameters file, see [Create Resource Manager parameters file](./parameter-files.md).
179+
Rather than passing parameters as inline values in your script, you might find it easier to use a parameters file, either a [Bicep parameters file](#bicep-parameters-files) or a [JSON parameters file](#json-parameters-files) that contains the parameter values. The parameters file must be a local file. External parameters files aren't supported with Azure CLI. For more information about the parameters file, see [Create Resource Manager parameters file](./parameter-files.md).
180180

181-
With Azure CLI version 2.53.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameter file. With the `using` statement within the Bicep parameters file, there's no need to provide the `--template-file` switch when specifying a Bicep parameter file for the `--parameters` switch. Including the `--template-file` switch will result in an "Only a .bicep template is allowed with a .bicepparam file" error.
181+
With Azure CLI version 2.53.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameters file. With the `using` statement within the Bicep parameters file, there's no need to provide the `--template-file` switch when specifying a Bicep parameters file for the `--parameters` switch. Including the `--template-file` switch will result in an "Only a .bicep template is allowed with a .bicepparam file" error.
182182

183183
The following example shows a parameters file named _storage.bicepparam_. The file is in the same directory where the command is run.
184184

@@ -189,7 +189,7 @@ az deployment group create \
189189
--parameters storage.bicepparam
190190
```
191191

192-
### JSON parameter files
192+
### JSON parameters files
193193

194194
The following example shows a parameters file named _storage.parameters.json_. The file is in the same directory where the command is run.
195195

0 commit comments

Comments
 (0)