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
description: Describes the different types of runbooks that you can use in Azure Automation and considerations that you should take into account when determining which type to use.
3
+
description: Describes the different types of runbooks that you can use in Azure Automation and considerations for determining which type to use.
4
4
services: automation
5
5
ms.subservice: process-automation
6
6
ms.date: 03/05/2019
7
7
ms.topic: conceptual
8
8
---
9
9
# Azure Automation runbook types
10
10
11
-
The Azure Automation process automation service supports several types of runbooks. The types are briefly defined in the following table and described in more detail in the sections below. To learn about the process automation environment, see [Runbook execution in Azure Automation](automation-runbook-execution.md).
11
+
The Azure Automation process automation service supports several types of runbooks, as defined in the following table. To learn about the process automation environment, see [Runbook execution in Azure Automation](automation-runbook-execution.md).
12
12
13
13
| Type | Description |
14
14
|:--- |:--- |
@@ -18,31 +18,34 @@ The Azure Automation process automation service supports several types of runboo
18
18
|[PowerShell Workflow](#powershell-workflow-runbooks)|Text runbook based on Windows PowerShell Workflow scripting. |
19
19
|[Python](#python-runbooks)|Text runbook based on Python scripting. |
20
20
21
-
## Graphical runbooks
21
+
Take into account the following considerations when determining which type to use for a particular runbook.
22
+
23
+
* You can't convert runbooks from graphical to text type, or the other way around.
24
+
* There are limitations when using runbooks of different types as child runbooks. For more information, see [Child runbooks in Azure Automation](automation-child-runbooks.md).
22
25
23
-
You can create and edit graphical and graphical PowerShell Workflow runbooks using the graphical editor in the Azure portal. However, you can't create or edit this type of runbook with another tool.
26
+
## Graphical runbooks
24
27
25
-
A graphical runbook has the following main features:
28
+
You can create and edit graphical and graphical PowerShell Workflow runbooks using the graphical editor in the Azure portal. However, you can't create or edit this type of runbook with another tool. Main features of graphical runbooks:
26
29
27
-
* Can be exported to a file in your Automation account and then imported into another Automation account.
28
-
*Generates PowerShell code.
29
-
* Can be converted to or from a graphical PowerShell Workflow runbook during import.
30
+
* Can be exported to files in your Automation account and then imported into another Automation account.
31
+
*Generate PowerShell code.
32
+
* Can be converted to or from graphical PowerShell Workflow runbooks during import.
*Include other runbooks as child runbooks to create high-level workflows.
40
+
*Encourage modular programming.
38
41
39
42
### Limitations
40
43
41
-
* Can't be created or edited outside of the Azure portal.
44
+
* Can't create or edit outside the Azure portal.
42
45
* Might require a code activity containing PowerShell code to execute complex logic.
43
-
* Can't be converted to one of the [text formats](automation-runbook-types.md), nor can a text runbook be converted to graphical format.
44
-
*Doesn't allow you to view or directly edit the PowerShell code that the graphical workflow creates. You can view the code you create in any code activities.
45
-
*Doesn't run on a Linux Hybrid Runbook Worker. See [Automate resources in your datacenter or cloud by using Hybrid Runbook Worker](automation-hybrid-runbook-worker.md).
46
+
* Can't convert to one of the [text formats](automation-runbook-types.md), nor can you convert a text runbook to graphical format.
47
+
*Can't view or directly edit PowerShell code that the graphical workflow creates. You can view the code you create in any code activities.
48
+
*Can't run runbooks on a Linux Hybrid Runbook Worker. See [Automate resources in your datacenter or cloud by using Hybrid Runbook Worker](automation-hybrid-runbook-worker.md).
46
49
47
50
## PowerShell runbooks
48
51
@@ -51,69 +54,62 @@ PowerShell runbooks are based on Windows PowerShell. You directly edit the code
51
54
### Advantages
52
55
53
56
* Implement all complex logic with PowerShell code without the additional complexities of PowerShell Workflow.
54
-
*Runbook starts faster than PowerShell Workflow runbooks since it doesn't need to be compiled before running.
55
-
*Can run in Azure or on both Linux and Windows Hybrid Runbook Workers
57
+
*Start faster than PowerShell Workflow runbooks, since they don't need to be compiled before running.
58
+
*Run in Azure and on Hybrid Runbook Workers for both Windows and Linux.
56
59
57
60
### Limitations
58
61
59
-
*Must be familiar with PowerShell scripting.
60
-
*Can't use [parallel processing](automation-powershell-workflow.md#parallel-processing) to execute multiple actions in parallel.
61
-
*Can't use [checkpoints](automation-powershell-workflow.md#checkpoints) to resume runbook if there is an error.
62
-
* PowerShell Workflow runbooks and Graphical runbooks can only be included as child runbooks by using the Start-AzureAutomationRunbook cmdlet, which creates a new job.
62
+
*You must be familiar with PowerShell scripting.
63
+
*Runbooks can't use [parallel processing](automation-powershell-workflow.md#parallel-processing) to execute multiple actions in parallel.
64
+
*Runbooks can't use [checkpoints](automation-powershell-workflow.md#checkpoints) to resume runbook if there's an error.
65
+
*You can include only PowerShell Workflow runbooks and graphical runbooks as child runbooks by using the [Start-AzAutomationRunbook](https://docs.microsoft.com/powershell/module/az.automation/start-azautomationrunbook?view=azps-3.7.0) cmdlet, which creates a new job.
63
66
64
-
### Known Issues
67
+
### Known issues
65
68
66
-
Following are current known issues with PowerShell runbooks.
69
+
The following are current known issues with PowerShell runbooks:
67
70
68
-
* PowerShell runbooks cannot retrieve an unencrypted [variable asset](automation-variables.md) with a null value.
69
-
* PowerShell runbooks can't retrieve a [variable asset](automation-variables.md) with *~* in the name.
70
-
* Get-Processin a loop in a PowerShell runbook may crash after about 80 iterations.
71
-
* A PowerShell runbook may fail if it attempts to write a large amount of data to the output stream at once. You can typically work around this issue by outputting just the information you need when working with large objects. For example, instead of outputting something like *Get-Process*, you can output just the required fields with *Get-Process | Select ProcessName, CPU*.
71
+
* PowerShell runbooks can't retrieve an unencrypted [variable asset](automation-variables.md) with a null value.
72
+
* PowerShell runbooks can't retrieve a variable asset with `*~*` in the name.
73
+
*A [Get-Process](https://docs.microsoft.com/powershell/module/microsoft.powershell.management/get-process?view=powershell-7) operation in a loop in a PowerShell runbook can crash after about 80 iterations.
74
+
* A PowerShell runbook can fail if it tries to write a large amount of data to the output stream at once. You can typically work around this issue by having the runbook output just the information needed to work with large objects. For example, instead of using `Get-Process` with no limitations, you can have the cmdlet output just the required parameters as in `Get-Process | Select ProcessName, CPU`.
72
75
73
76
## PowerShell Workflow runbooks
74
77
75
-
PowerShell Workflow runbooks are text runbooks based on [Windows PowerShell Workflow](automation-powershell-workflow.md). You directly edit the code of the runbook using the text editor in the Azure portal. You can also use any offline text editor and [import the runbook](manage-runbooks.md) into Azure Automation.
78
+
PowerShell Workflow runbooks are text runbooks based on [Windows PowerShell Workflow](automation-powershell-workflow.md). You directly edit the code of the runbook using the text editor in the Azure portal. You can also use any offline text editor and [import the runbook](manage-runbooks.md) into Azure Automation.
76
79
77
80
### Advantages
78
81
79
82
* Implement all complex logic with PowerShell Workflow code.
80
-
* Use [checkpoints](automation-powershell-workflow.md#checkpoints) to resume runbook if there is an error.
81
-
* Use [parallel processing](automation-powershell-workflow.md#parallel-processing) to perform multiple actions in parallel.
82
-
* Can include other Graphical runbooks and PowerShell Workflow runbooks as child runbooks to create high-level workflows.
83
+
* Use [checkpoints](automation-powershell-workflow.md#checkpoints) to resume operation if there's an error.
84
+
* Use [parallel processing](automation-powershell-workflow.md#parallel-processing) to do multiple actions in parallel.
85
+
* Can include other graphical runbooks and PowerShell Workflow runbooks as child runbooks to create high-level workflows.
83
86
84
87
### Limitations
85
88
86
-
*Author must be familiar with PowerShell Workflow.
87
-
*Runbook must deal with the additional complexity of PowerShell Workflow such as [deserialized objects](automation-powershell-workflow.md#code-changes).
88
-
*Runbook takes longer to start than PowerShell runbooks since it needs to be compiled before running.
89
-
*PowerShell runbooks can only be included as child runbooks by using the Start-AzureAutomationRunbook cmdlet, which creates a new job.
90
-
*Can't run on a Linux Hybrid Runbook Worker.
89
+
*You must be familiar with PowerShell Workflow.
90
+
*Runbooks must deal with the additional complexity of PowerShell Workflow, such as [deserialized objects](automation-powershell-workflow.md#code-changes).
91
+
*Runbooks take longer to start than PowerShell runbooks since they must be compiled before running.
92
+
*You can only include PowerShell runbooks as child runbooks by using the `Start-AzAutomationRunbook` cmdlet.
93
+
*Runbooks can't run on a Linux Hybrid Runbook Worker.
91
94
92
95
## Python runbooks
93
96
94
-
Python runbooks compile under Python 2. You can directly edit the code of the runbook using the text editor in the Azure portal, or with an offline text editor and [import the runbook](manage-runbooks.md) into Azure Automation.
97
+
Python runbooks compile under Python 2. You can directly edit the code of the runbook using the text editor in the Azure portal. You can also use an offline text editor and [import the runbook](manage-runbooks.md) into Azure Automation.
95
98
96
99
### Advantages
97
100
98
-
*Utilize the robust Python libraries.
99
-
* Can run in Azure or on both Linux Hybrid Runbook Workers. Windows Hybrid Runbook Workers are supported with [python2.7](https://www.python.org/downloads/release/latest/python2) installed.
101
+
*Use the robust Python libraries.
102
+
* Can run in Azure or on Linux Hybrid Runbook Workers. Windows Hybrid Runbook Workers are supported with [python2.7](https://www.python.org/downloads/release/latest/python2) installed.
100
103
101
104
### Limitations
102
105
103
-
* Must be familiar with Python scripting.
104
-
* Only Python 2 is supported at the moment, meaning Python 3 specific functions will fail.
105
-
* To use third-party libraries, you must [import the package](python-packages.md) into the Automation account for it to be used.
106
-
107
-
## Considerations
108
-
109
-
Take into account the following additional considerations when determining which type to use for a particular runbook.
110
-
111
-
* You can't convert runbooks from graphical to textual type or the other way around.
112
-
* There are limitations using runbooks of different types as a child runbook. For more information, see [Child runbooks in Azure Automation](automation-child-runbooks.md).
106
+
* You must be familiar with Python scripting.
107
+
* Only Python 2 is supported presently. Any Python 3-specific functions fail.
108
+
* To use third-party libraries, you must [import the packages](python-packages.md) into the Automation account.
113
109
114
110
## Next steps
115
111
116
-
* To learn more about Graphical runbook authoring, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md)
117
-
* To understand the differences between PowerShell and PowerShell workflows for runbooks, see [Learning Windows PowerShell Workflow](automation-powershell-workflow.md)
118
-
* For more information on how to create or import a Runbook, see [Creating or Importing a Runbook](manage-runbooks.md)
119
-
*For more information on PowerShell, including language reference and learning modules, refer to the [PowerShell Docs](https://docs.microsoft.com/powershell/scripting/overview).
112
+
* To learn more about graphical runbook authoring, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
113
+
* To understand the differences between PowerShell and PowerShell workflows for runbooks, see [Learning Windows PowerShell Workflow](automation-powershell-workflow.md).
114
+
* For more information on how to create or import a runbook, see [Manage runbooks in Azure Automation](manage-runbooks.md).
115
+
*To find out more about PowerShell, including language reference and learning modules, refer to the [PowerShell Docs](https://docs.microsoft.com/powershell/scripting/overview).
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-remove-tls-10-11.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
@@ -48,7 +48,7 @@ Most applications use Redis client libraries to handle communication with their
48
48
Redis .NET clients use the earliest TLS version by default on .NET Framework 4.5.2 or earlier, and use the latest TLS version on .NET Framework 4.6 or later. If you're using an older version of .NET Framework, you can enable TLS 1.2 manually:
49
49
50
50
***StackExchange.Redis:** Set `ssl=true` and `sslprotocols=tls12` in the connection string.
51
-
***ServiceStack.Redis:** Follow the [ServiceStack.Redis instructions](https://github.com/ServiceStack/ServiceStack.Redis/pull/247).
51
+
***ServiceStack.Redis:** Follow the [ServiceStack.Redis instructions](https://github.com/ServiceStack/ServiceStack.Redis#servicestackredis-ssl-support).
* Azure Databricks roles-based access enables fine-grained user permissions for notebooks, clusters, jobs, and data.
82
82
* Enterprise-grade SLAs.
83
83
84
+
> [!IMPORTANT]
85
+
>
86
+
> Azure Databricks is a Microsoft Azure first-party service that is deployed on the Global Azure Public Cloud infrastructure. All communications between components of the service, including between the public IPs in the control plane and the customer data plane, remain within the Microsoft Azure network backbone. See also [Microsoft global network](https://docs.microsoft.com/azure/networking/microsoft-global-network).
87
+
88
+
84
89
## Integration with Azure services
85
90
86
91
Azure Databricks integrates deeply with Azure databases and stores: SQL Data Warehouse, Cosmos DB, Data Lake Store, and Blob Storage.
Copy file name to clipboardExpand all lines: articles/azure-portal/azure-portal-safelist-urls.md
+2-11Lines changed: 2 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,13 @@ services: azure-portal
5
5
keywords:
6
6
author: mgblythe
7
7
ms.author: mblythe
8
-
ms.date: 01/29/2020
8
+
ms.date: 04/10/2020
9
9
ms.topic: conceptual
10
10
11
11
ms.service: azure-portal
12
12
manager: mtillman
13
13
---
14
+
14
15
# Safelist the Azure portal URLs on your firewall or proxy server
15
16
16
17
You can configure on-premises security devices to bypass security restrictions for the Azure portal URLs. This configuration can improve performance and connectivity between your local- or wide-area network and the Azure cloud.
@@ -75,13 +76,3 @@ The URL endpoints to safelist for the Azure portal are specific to the Azure clo
75
76
> Traffic to these endpoints uses standard TCP ports for HTTP (80) and HTTPS (443).
76
77
>
77
78
>
78
-
## Next steps
79
-
80
-
Need to safelist IP addresses? Download the list of Microsoft Azure datacenter IP ranges for your cloud:
Other Microsoft services use additional URLs and IP addresses for connectivity. To optimize network connectivity for Microsoft 365 services, see [Set up your network for Office 365](/office365/enterprise/set-up-network-for-office-365).
0 commit comments