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
Copy file name to clipboardExpand all lines: articles/azure-arc/servers/prepare-extended-security-updates.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,12 +43,12 @@ To prepare for this new offer, you need to plan and prepare to onboard your mach
43
43
We recommend you deploy your machines to Azure Arc in preparation for when the related Azure services deliver supported functionality to manage ESU. Once these machines are onboarded to Azure Arc-enabled servers, you'll have visibility into their ESU coverage and enroll through the Azure portal or using Azure Policy one month before Windows Server 2012 end of support. Billing for this service starts from October 2023, after Windows Server 2012 end of support.
44
44
45
45
> [!NOTE]
46
-
> In order to purchase ESUs, you must have Software Assurance through Volume Licensing Programs such as an Enterprise Agreement (EA), Enterprise Agreement Subscription (EAS), Enrollment for Education Solutions (EES), or Server and Cloud Enrollment (SCE).
46
+
> In order to purchase ESUs, you must have Software Assurance through Volume Licensing Programs such as an Enterprise Agreement (EA), Enterprise Agreement Subscription (EAS), Enrollment for Education Solutions (EES), or Server and Cloud Enrollment (SCE). Alternatively, if your Windows Server 2012/2012 R2 machines are licensed through SPLA or with a Server Subscription, Software Assurance is not required to purchase ESUs.
47
47
>
48
48
## Next steps
49
49
50
50
* Find out more about [planning for Windows Server and SQL Server end of support](https://www.microsoft.com/en-us/windows-server/extended-security-updates) and [getting Extended Security Updates](/windows-server/get-started/extended-security-updates-deploy).
51
51
52
52
* Learn about best practices and design patterns through the [Azure Arc landing zone accelerator for hybrid and multicloud](/azure/cloud-adoption-framework/scenarios/hybrid/arc-enabled-servers/eslz-identity-and-access-management).
53
53
* Learn more about [Arc-enabled servers](overview.md) and how they work with Azure through the Azure Connected Machine agent.
54
-
* Explore options for [onboarding your machines](plan-at-scale-deployment.md) to Azure Arc-enabled servers.
54
+
* Explore options for [onboarding your machines](plan-at-scale-deployment.md) to Azure Arc-enabled servers.
Check the ‘Heartbeat’ table (and other tables you configured in the rules) in the Log Analytics workspace that you specified as a destination in the data collection rule(s).
396
+
The `SourceComputerId`, `Computer`, `ComputerIP` columns should all reflect the client device information respectively, and the `Category` column should say 'Azure Monitor Agent'. See example below:
397
+
398
+
[](media/azure-monitor-agent-windows-client/azure-monitor-agent-heartbeat-logs.png)
394
399
395
400
### Using PowerShell for offboarding
396
401
```PowerShell
397
402
#This will remove the monitor object
398
-
$TenantID = "xxxxxxxxx-xxxx-xxx" #Your Tenant ID
399
-
$SubscriptionID = "xxxxxx-xxxx-xxxxx" #Your Subscription ID
$MonitoredObjectAssociations = Invoke-RestMethod -Uri $requestURL -Headers $AuthenticationHeader -Method Get
412
422
413
-
## Verify successful setup
414
-
Check the ‘Heartbeat’ table (and other tables you configured in the rules) in the Log Analytics workspace that you specified as a destination in the data collection rule(s).
415
-
The `SourceComputerId`, `Computer`, `ComputerIP` columns should all reflect the client device information respectively, and the `Category` column should say 'Azure Monitor Agent'. See example below:
423
+
#Disassociate from all Data Collection Rule
424
+
foreach ($Association in $MonitoredObjectAssociations.value){
if %ERRORLEVEL% NEQ 0 if %retryCount% NEQ %maxRetry% goto loop
209
+
if %ERRORLEVEL% NEQ 0 if %retryCount%== %maxRetry% echo Taking existing file to install since error occurred while downloading .NET framework %netfx% setup from %netfxUrl%. >> %startuptasklog%
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-private-link.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.date: 10/11/2022
10
10
11
11
# Connect privately to an Azure container registry using Azure Private Link
12
12
13
-
Limit access to a registry by assigning virtual network private IP addresses to the registry endpoints and using [Azure Private Link](../private-link/private-link-overview.md). Network traffic between the clients on the virtual network and the registry's private endpoints traverses the virtual network and a private link on the Microsoft backbone network, eliminating exposure from the public internet. Private Link also enables private registry access from on-premises through [Azure ExpressRoute](../expressroute/expressroute-introduction.MD) private peering or a [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md).
13
+
Limit access to a registry by assigning virtual network private IP addresses to the registry endpoints and using [Azure Private Link](../private-link/private-link-overview.md). Network traffic between the clients on the virtual network and the registry's private endpoints traverses the virtual network and a private link on the Microsoft backbone network, eliminating exposure from the public internet. Private Link also enables private registry access from on-premises through [Azure ExpressRoute](../expressroute/expressroute-introduction.md), private peering, or a [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md).
14
14
15
15
You can [configure DNS settings](../private-link/private-endpoint-overview.md#dns-configuration) for the registry's private endpoints, so that the settings resolve to the registry's allocated private IP address. With DNS configuration, clients and services in the network can continue to access the registry at the registry's fully qualified domain name, such as *myregistry.azurecr.io*.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-debug-pipeline-reuse-issues.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,8 @@ Azure Machine Learning pipeline has holistic logic to calculate whether a compon
36
36
37
37
Reuse criteria:
38
38
39
-
-Compenet defintion`is_determinstic` = true
40
-
-Popeline runtime setting `FocceReRun` = false
39
+
-Component definition`is_determinstic` = true
40
+
-Pipeline runtime setting `ForceReRun` = false
41
41
- Component code, environment definition, inputs and parameters, output settings, and run settings are all the same.
42
42
43
43
If a component meets the reuse criteria, the pipeline service skips execution for the component, copies original component's status, displays original component's output/logs/metrics for the reused component. In the pipeline UI, the reused component shows a little recycle icon to indicate this component has been reused.
@@ -100,4 +100,4 @@ You can compare the input data, parameters, output settings, run settings of the
100
100
101
101
### Step 6: Contact Microsoft for support
102
102
103
-
If you follow all above steps, and you still can't find the root cause of unexpected rerun, you can [file a support case ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) to Microsoft to get help.
103
+
If you follow all above steps, and you still can't find the root cause of unexpected rerun, you can [file a support case ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) to Microsoft to get help.
Copy file name to clipboardExpand all lines: articles/service-connector/quickstart-portal-spring-cloud-connection.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ You'll use Service Connector to create a new service connection in Azure Spring
56
56
|**Subscription**|*my-subscription*| The subscription that contains your target service (the service you want to connect to). The default value is the subscription that contains the app deployed to Azure Spring Apps. |
57
57
|**Connection name**|*storageblob_17d38*| The connection name that identifies the connection between your app and target service. Use the connection name provided by Service Connector or enter your own connection name. |
58
58
|**Storage account**|*my-storage-account*| The target storage account you want to connect to. If you choose a different service type, select the corresponding target service instance. |
59
-
|**Client type**|*SpringBoot*| The application stack that works with the target service you selected. Choose between SpringBoot and Java. |
59
+
|**Client type**|*SpringBoot*| The application stack that works with the target service you selected. Besides SpringBoot and Java, other stacks are also supported.|
60
60
61
61
:::image type="content" source="./media/azure-spring-apps-quickstart/basics.png" alt-text="Screenshot of the Azure portal, filling out the Basics tab.":::
0 commit comments