@pulumi/azure 5.90.0-alpha.1724930750 → 5.90.0-alpha.1725648351

package/appservice/appService.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "../types/output";
 /**
  * Manages an App Service (within an App Service Plan).
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebApp` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` resources instead.
  *
  * > **Note:** When using Slots - the `appSettings`, `connectionString` and `siteConfig` blocks on the `azure.appservice.AppService` resource will be overwritten when promoting a Slot using the `azure.appservice.ActiveSlot` resource.
  *

package/appservice/appService.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages an App Service (within an App Service Plan).
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebApp` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` resources instead.
  *
  * > **Note:** When using Slots - the `appSettings`, `connectionString` and `siteConfig` blocks on the `azure.appservice.AppService` resource will be overwritten when promoting a Slot using the `azure.appservice.ActiveSlot` resource.
  *

package/appservice/functionApp.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "../types/output";
 /**
  * Manages a Function App.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionApp` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` resources instead.
  *
  * > **Note:** To connect an Azure Function App and a subnet within the same region `azure.appservice.VirtualNetworkSwiftConnection` can be used.
  * For an example, check the `azure.appservice.VirtualNetworkSwiftConnection` documentation.

package/appservice/functionApp.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages a Function App.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionApp` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` resources instead.
  *
  * > **Note:** To connect an Azure Function App and a subnet within the same region `azure.appservice.VirtualNetworkSwiftConnection` can be used.
  * For an example, check the `azure.appservice.VirtualNetworkSwiftConnection` documentation.

package/appservice/functionAppSlot.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "../types/output";
 /**
  * Manages a Function App deployment Slot.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionAppSlot` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionAppSlot` and `azure.appservice.WindowsFunctionAppSlot` resources instead.
  *
  * ## Example Usage
  *

package/appservice/functionAppSlot.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages a Function App deployment Slot.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionAppSlot` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxFunctionAppSlot` and `azure.appservice.WindowsFunctionAppSlot` resources instead.
  *
  * ## Example Usage
  *

package/appservice/getAppService.d.ts

@@ -3,7 +3,7 @@ import * as outputs from "../types/output";
 /**
  * Use this data source to access information about an existing App Service.
  *
- * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` data sources instead.
+ * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` data sources instead.
  *
  * ## Example Usage
  *
@@ -122,7 +122,7 @@ export interface GetAppServiceResult {
 /**
  * Use this data source to access information about an existing App Service.
  *
- * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` data sources instead.
+ * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` data sources instead.
  *
  * ## Example Usage
  *

package/appservice/getAppService.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Use this data source to access information about an existing App Service.
  *
- * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` data sources instead.
+ * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` data sources instead.
  *
  * ## Example Usage
  *
@@ -34,7 +34,7 @@ exports.getAppService = getAppService;
 /**
  * Use this data source to access information about an existing App Service.
  *
- * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` data sources instead.
+ * !> **Note:** The `azure.appservice.AppService` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxWebApp` and `azure.appservice.WindowsWebApp` data sources instead.
  *
  * ## Example Usage
  *

package/appservice/getFunctionApp.d.ts

@@ -3,7 +3,7 @@ import * as outputs from "../types/output";
 /**
  * Use this data source to access information about a Function App.
  *
- * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` data sources instead.
+ * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` data sources instead.
  *
  * ## Example Usage
  *
@@ -110,7 +110,7 @@ export interface GetFunctionAppResult {
 /**
  * Use this data source to access information about a Function App.
  *
- * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` data sources instead.
+ * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` data sources instead.
  *
  * ## Example Usage
  *

package/appservice/getFunctionApp.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Use this data source to access information about a Function App.
  *
- * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` data sources instead.
+ * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` data sources instead.
  *
  * ## Example Usage
  *
@@ -34,7 +34,7 @@ exports.getFunctionApp = getFunctionApp;
 /**
  * Use this data source to access information about a Function App.
  *
- * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` data sources instead.
+ * !> **Note:** The `azure.appservice.FunctionApp` data source is deprecated in version 3.0 of the AzureRM provider and will be removed in version 4.0. Please use the `azure.appservice.LinuxFunctionApp` and `azure.appservice.WindowsFunctionApp` data sources instead.
  *
  * ## Example Usage
  *

package/appservice/hybridConnection.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * Manages an App Service Hybrid Connection for an existing App Service, Relay and Service Bus.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.FunctionAppHybridConnection` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.FunctionAppHybridConnection` and `azure.appservice.WebAppHybridConnection` resources instead.
  *
  * ## Example Usage
  *

package/appservice/hybridConnection.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages an App Service Hybrid Connection for an existing App Service, Relay and Service Bus.
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.FunctionAppHybridConnection` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.FunctionAppHybridConnection` and `azure.appservice.WebAppHybridConnection` resources instead.
  *
  * ## Example Usage
  *

package/appservice/slot.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "../types/output";
 /**
  * Manages an App Service Slot (within an App Service).
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebAppSlot` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebAppSlot` and `azure.appservice.WindowsWebAppSlot` resources instead.
  *
  * > **Note:** When using Slots - the `appSettings`, `connectionString` and `siteConfig` blocks on the `azure.appservice.AppService` resource will be overwritten when promoting a Slot using the `azure.appservice.ActiveSlot` resource.
  *

package/appservice/slot.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages an App Service Slot (within an App Service).
  *
- * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebAppSlot` resources instead.
+ * !> **NOTE:** This resource has been deprecated in version 5.0 of the provider and will be removed in version 6.0. Please use `azure.appservice.LinuxWebAppSlot` and `azure.appservice.WindowsWebAppSlot` resources instead.
  *
  * > **Note:** When using Slots - the `appSettings`, `connectionString` and `siteConfig` blocks on the `azure.appservice.AppService` resource will be overwritten when promoting a Slot using the `azure.appservice.ActiveSlot` resource.
  *

package/cdn/endpoint.d.ts

@@ -4,7 +4,7 @@ import * as outputs from "../types/output";
 /**
  * A CDN Endpoint is the entity within a CDN Profile containing configuration information regarding caching behaviours and origins. The CDN Endpoint is exposed using the URL format `<endpointname>.azureedge.net`.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and FrontDoor resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/cdn/endpoint.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * A CDN Endpoint is the entity within a CDN Profile containing configuration information regarding caching behaviours and origins. The CDN Endpoint is exposed using the URL format `<endpointname>.azureedge.net`.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and FrontDoor resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/cdn/profile.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * Manages a CDN Profile to create a collection of CDN Endpoints.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and FrontDoor resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/cdn/profile.js

@@ -8,7 +8,7 @@ const utilities = require("../utilities");
 /**
  * Manages a CDN Profile to create a collection of CDN Endpoints.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and FrontDoor resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/compute/windowsVirtualMachine.d.ts

@@ -186,7 +186,7 @@ export declare class WindowsVirtualMachine extends pulumi.CustomResource {
     /**
      * Should the VM be patched without requiring a reboot? Possible values are `true` or `false`. Defaults to `false`. For more information about hot patching please see the [product documentation](https://docs.microsoft.com/azure/automanage/automanage-hotpatch).
      *
-     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a Azure generation 2 directory within the GitHub Repository.
+     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a [Azure generation 2](https://docs.microsoft.com/azure/virtual-machines/generation-2#generation-2-vm-sizes) VM. An example of how to correctly configure a Windows Virtual Machine to use the `hotpatchingEnabled` field can be found in the `./examples/virtual-machines/windows/hotpatching-enabled` directory within the GitHub Repository.
      */
     readonly hotpatchingEnabled: pulumi.Output<boolean | undefined>;
     /**
@@ -459,7 +459,7 @@ export interface WindowsVirtualMachineState {
     /**
      * Should the VM be patched without requiring a reboot? Possible values are `true` or `false`. Defaults to `false`. For more information about hot patching please see the [product documentation](https://docs.microsoft.com/azure/automanage/automanage-hotpatch).
      *
-     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a Azure generation 2 directory within the GitHub Repository.
+     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a [Azure generation 2](https://docs.microsoft.com/azure/virtual-machines/generation-2#generation-2-vm-sizes) VM. An example of how to correctly configure a Windows Virtual Machine to use the `hotpatchingEnabled` field can be found in the `./examples/virtual-machines/windows/hotpatching-enabled` directory within the GitHub Repository.
      */
     hotpatchingEnabled?: pulumi.Input<boolean>;
     /**
@@ -724,7 +724,7 @@ export interface WindowsVirtualMachineArgs {
     /**
      * Should the VM be patched without requiring a reboot? Possible values are `true` or `false`. Defaults to `false`. For more information about hot patching please see the [product documentation](https://docs.microsoft.com/azure/automanage/automanage-hotpatch).
      *
-     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a Azure generation 2 directory within the GitHub Repository.
+     * > **NOTE:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, and the VM's `size` is set to a [Azure generation 2](https://docs.microsoft.com/azure/virtual-machines/generation-2#generation-2-vm-sizes) VM. An example of how to correctly configure a Windows Virtual Machine to use the `hotpatchingEnabled` field can be found in the `./examples/virtual-machines/windows/hotpatching-enabled` directory within the GitHub Repository.
      */
     hotpatchingEnabled?: pulumi.Input<boolean>;
     /**

package/frontdoor/customHttpsConfiguration.d.ts

@@ -12,7 +12,7 @@ import * as outputs from "../types/output";
  *
  * !> **BREAKING CHANGE:** The `resourceGroupName` field has been removed as of the `v2.58.0` provider release. If the `resourceGroupName` field has been defined in your current `azure.frontdoor.CustomHttpsConfiguration` resource configuration file please remove it else you will receive a `An argument named "resourceGroupName" is not expected here.` error. If your pre-existing Front Door instance contained inline `customHttpsConfiguration` blocks there are additional steps that will need to be completed to successfully migrate your Front Door onto the `v2.58.0` provider which can be found in this guide.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and Front Door resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ```typescript
  * import * as pulumi from "@pulumi/pulumi";

package/frontdoor/customHttpsConfiguration.js

@@ -16,7 +16,7 @@ const utilities = require("../utilities");
  *
  * !> **BREAKING CHANGE:** The `resourceGroupName` field has been removed as of the `v2.58.0` provider release. If the `resourceGroupName` field has been defined in your current `azure.frontdoor.CustomHttpsConfiguration` resource configuration file please remove it else you will receive a `An argument named "resourceGroupName" is not expected here.` error. If your pre-existing Front Door instance contained inline `customHttpsConfiguration` blocks there are additional steps that will need to be completed to successfully migrate your Front Door onto the `v2.58.0` provider which can be found in this guide.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and Front Door resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ```typescript
  * import * as pulumi from "@pulumi/pulumi";

package/frontdoor/firewallPolicy.d.ts

@@ -6,7 +6,7 @@ import * as outputs from "../types/output";
  *
  * Manages an Azure Front Door (classic) Web Application Firewall Policy instance.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and Front Door resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/frontdoor/firewallPolicy.js

@@ -10,7 +10,7 @@ const utilities = require("../utilities");
  *
  * Manages an Azure Front Door (classic) Web Application Firewall Policy instance.
  *
- * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue as the necessary changes are identified.
+ * !> **Be Aware:** Azure is rolling out a breaking change on Friday 9th April 2021 which may cause issues with the CDN/FrontDoor resources. More information is available in this GitHub issue - however unfortunately this may necessitate a breaking change to the CDN and Front Door resources, more information will be posted in the GitHub issue as the necessary changes are identified.
  *
  * ## Example Usage
  *

package/logicapps/triggerCustom.d.ts

@@ -60,7 +60,7 @@ export declare class TriggerCustom extends pulumi.CustomResource {
      */
     readonly body: pulumi.Output<string>;
     /**
-     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitor_action_group.
+     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitorActionGroup and security_center_automation.
      */
     readonly callbackUrl: pulumi.Output<string>;
     /**
@@ -91,7 +91,7 @@ export interface TriggerCustomState {
      */
     body?: pulumi.Input<string>;
     /**
-     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitor_action_group.
+     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitorActionGroup and security_center_automation.
      */
     callbackUrl?: pulumi.Input<string>;
     /**

package/logicapps/triggerHttpRequest.d.ts

@@ -57,7 +57,7 @@ export declare class TriggerHttpRequest extends pulumi.CustomResource {
      */
     static isInstance(obj: any): obj is TriggerHttpRequest;
     /**
-     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitor_action_group.
+     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitorActionGroup and security_center_automation.
      */
     readonly callbackUrl: pulumi.Output<string>;
     /**
@@ -98,7 +98,7 @@ export declare class TriggerHttpRequest extends pulumi.CustomResource {
  */
 export interface TriggerHttpRequestState {
     /**
-     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitor_action_group.
+     * The URL of the Trigger within the Logic App Workflow. For use with certain resources like monitorActionGroup and security_center_automation.
      */
     callbackUrl?: pulumi.Input<string>;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/azure",
-    "version": "5.90.0-alpha.1724930750",
+    "version": "5.90.0-alpha.1725648351",
     "description": "A Pulumi package for creating and managing Microsoft Azure cloud resources, based on the Terraform azurerm provider. We recommend using the [Azure Native provider](https://github.com/pulumi/pulumi-azure-native) to provision Azure infrastructure. Azure Native provides complete coverage of Azure resources and same-day access to new resources and resource updates.",
     "keywords": [
         "pulumi",
@@ -30,6 +30,6 @@
     "pulumi": {
         "resource": true,
         "name": "azure",
-        "version": "5.90.0-alpha.1724930750"
+        "version": "5.90.0-alpha.1725648351"
     }
 }

package/types/input.d.ts

@@ -18905,7 +18905,7 @@ export declare namespace compute {
         /**
          * Should the VM be patched without requiring a reboot? Possible values are `true` or `false`. Defaults to `false`. For more information about hot patching please see the [product documentation](https://docs.microsoft.com/azure/automanage/automanage-hotpatch).
          *
-         * > **Note:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, the VM's `skuName` is set to a Azure generation 2 directory within the GitHub Repository.
+         * > **Note:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, the VM's `skuName` is set to a [Azure generation 2](https://docs.microsoft.com/azure/virtual-machines/generation-2#generation-2-vm-sizes) VM SKU and the `extension` contains an application health extension. An example of how to correctly configure a Virtual Machine Scale Set to provision a Windows Virtual Machine with hotpatching enabled can be found in the `./examples/orchestrated-vm-scale-set/hotpatching-enabled` directory within the GitHub Repository.
          */
         hotpatchingEnabled?: pulumi.Input<boolean>;
         /**

package/types/output.d.ts

@@ -25527,7 +25527,7 @@ export declare namespace compute {
         /**
          * Should the VM be patched without requiring a reboot? Possible values are `true` or `false`. Defaults to `false`. For more information about hot patching please see the [product documentation](https://docs.microsoft.com/azure/automanage/automanage-hotpatch).
          *
-         * > **Note:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, the VM's `skuName` is set to a Azure generation 2 directory within the GitHub Repository.
+         * > **Note:** Hotpatching can only be enabled if the `patchMode` is set to `AutomaticByPlatform`, the `provisionVmAgent` is set to `true`, your `sourceImageReference` references a hotpatching enabled image, the VM's `skuName` is set to a [Azure generation 2](https://docs.microsoft.com/azure/virtual-machines/generation-2#generation-2-vm-sizes) VM SKU and the `extension` contains an application health extension. An example of how to correctly configure a Virtual Machine Scale Set to provision a Windows Virtual Machine with hotpatching enabled can be found in the `./examples/orchestrated-vm-scale-set/hotpatching-enabled` directory within the GitHub Repository.
          */
         hotpatchingEnabled?: boolean;
         /**