By creating a feed view named "release" and setting it as the default view, packages that are published to the feed will not be immediately available for consumption. After the 9pm packages are tested successfully,you can configure a release pipeline that promotes a package to the @release view. This ensures that only tested packages are available for consumption and minimizes development effort as it doesn't require any additional steps to be taken by the consumerof the feed.
Reference:
Azure DevOps Docs: Create a feed and viewshttps://docs.microsoft.com/en-us/azure/devops/artifacts/feeds
/create-feed?view=azure-devops
Azure DevOps Docs: Promote a packagehttps://docs.microsoft.com/en-us/azure/devops/artifacts/feeds
/promote-package?view=azure-devops

The Custom ScriptExtension downloads and executes scripts on Azure virtual machines. This extension is useful for post deployment configuration, software installation, or any other configuration or management tasks. Scripts can be downloaded from Azure storage or GitHub, or provided to the Azure portal at extension run time. The Custom Script Extension integrates with Azure Resource Manager templates, and can be run using the Azure CLI, PowerShell, Azure portal, or the Azure Virtual Machine REST API.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows

See explanation below
Explanation:
Task 6: Create a Service Connection for Resource Group Deployment using Managed Identity and Workload Identity Federation Step 1: Understand the Requirements
* You want to deploy resources in the RGHod489Q1628 resource group.
* The service connection must:
* Use the ManagedJd1 managed identity.
* Use workload identity federation (OIDC-based authentication for enhanced security).
Step 2: Verify Prerequisites
* You need to ensure:
* The ManagedJd1 managed identity exists in your Azure subscription.
* Your Azure DevOps project (Project1) is linked to an Azure Active Directory tenant (for OIDC support).
* You have the Owner or User Access Administrator role on the RGHod489Q1628 resource group.
Step 3: Assign Role to Managed Identity
* Go to the Azure Portal.
* In the search bar, type Managed Identities and select Managed Identities.
* Locate and click on the ManagedJd1 identity.
* In the left menu, click Azure role assignments.
* Click + Add role assignment.
* Set the following:
* Scope: Resource Group
* Subscription: Your subscription
* Resource Group: RGHod489Q1628
* Role: Contributor (or appropriate role)
* Click Save.
This step ensures ManagedJd1 has permissions to deploy resources to RGHod489Q1628.
Step 4: Create a Federated Credential for Workload Identity Federation
* In the Azure Portal, navigate to the ManagedJd1 managed identity.
* In the left menu, click Workload identity federation (preview).
* Click + Add a federated credential.
* Configure as follows:
* Federated credential name: devops-oidc
* Issuer: https://vstoken.actions.githubusercontent.com (or use the default https://pipelines.actions.
githubusercontent.com for Azure DevOps)
* Subject identifier: Use the following format for Azure DevOps:
css
Copy
system:azuredevops:{organizationName}:{projectName}
For example:
css
Copy
system:azuredevops:{YourOrganizationName}:{Project1}
* Audience: api://AzureADTokenExchange
* Click Add.
This federated credential establishes trust between your Azure DevOps project and the managed identity.
Step 5: Create a Service Connection in Azure DevOps
* Go to your Azure DevOps project (Project1) in the browser.
* In the left menu, click Project settings.
* Under Pipelines, click Service connections.
* Click New service connection.
* Choose Azure Resource Manager.
* Choose the authentication method:
* Select Workload identity federation.
* Configure the service connection:
* Scope level: Resource Group.
* Resource Group: RGHod489Q1628.
* Subscription: Your subscription.
* Authentication method: Managed Identity with workload identity federation.
* Managed Identity: Enter the client ID or select ManagedJd1.
* Service connection name: e.g., Project1-RGHod489Q1628-Conn.
* Grant access permission to all pipelines (recommended).
* Click Save.
Step 6: Validate the Service Connection
* After creation, click on the new service connection to Verify it.
* Ensure the connection test is successful.
* You can now use this service connection in your pipelines for deploying resources to RGHod489Q1628.

Explanation:

Box 1: Hosted macOS
HostedmacOS pool (Azure Pipelines only): Enables you to build and release on macOS without having to configure a self-hosted macOS agent. This option affects where your data is stored.
Box 2: Hosted
Hosted pool (Azure Pipelines only): The Hosted pool is the built-in pool that is a collection of Microsoft- hosted agents.
References:https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx