|
7 | 7 | The `SqlAgentAlert` DSC resource is used to create, modify, or remove |
8 | 8 | _SQL Server Agent_ alerts. |
9 | 9 |
|
10 | | - An alert can be switch between using system message and severity-based alerts by passing |
11 | | - the required parameter. It will switch the alert type accordingly. |
| 10 | + An alert can be switched between a system-message–based alert and a severity-based |
| 11 | + alert by specifying the corresponding parameter. The alert type will be switched |
| 12 | + accordingly. |
12 | 13 |
|
13 | 14 | The built-in parameter **PSDscRunAsCredential** can be used to run the resource |
14 | 15 | as another user. The resource will then authenticate to the _SQL Server_ |
15 | | - instance as that user. It also possible to instead use impersonation by the |
16 | | - parameter **Credential**. |
| 16 | + instance as that user. It is also possible to use impersonation via the |
| 17 | + **Credential** parameter. |
17 | 18 |
|
18 | 19 | ## Requirements |
19 | 20 |
|
|
31 | 32 | When using the built-in parameter **PSDscRunAsCredential** the read-only |
32 | 33 | property **Reasons** will return empty values for the properties **Code** |
33 | 34 | and **Phrase**. The built-in property **PSDscRunAsCredential** does not work |
34 | | - together with class-based resources that using advanced type like the parameter |
35 | | - **Reasons** have. |
| 35 | + together with class-based resources that use advanced types, such as the |
| 36 | + **Reasons** parameter. |
36 | 37 |
|
37 | 38 | ### Using **Credential** property |
38 | 39 |
|
39 | | - SQL Authentication and Group Managed Service Accounts is not supported as |
40 | | - impersonation credentials. Currently only Windows Integrated Security is |
41 | | - supported to use as credentials. |
| 40 | + SQL Authentication and Group Managed Service Accounts are not supported as |
| 41 | + impersonation credentials. Currently, only Windows Integrated Security is |
| 42 | + supported. |
42 | 43 |
|
43 | 44 | For Windows Authentication the username must either be provided with the User |
44 | | - Principal Name (UPN), e.g. `[email protected]` or if using non-domain |
45 | | - (for example a local Windows Server account) account the username must be |
46 | | - provided without the NetBIOS name, e.g. `username`. Using the NetBIOS name, e.g |
47 | | - using the format `DOMAIN\username` will not work. |
| 45 | + Principal Name (UPN), e.g., `[email protected]`, or, if using a non‑domain |
| 46 | + account (for example, a local Windows Server account), the username must be |
| 47 | + provided without the NetBIOS name, e.g., `username`. Using the NetBIOS name, |
| 48 | + for example `DOMAIN\username`, will not work. |
48 | 49 |
|
49 | 50 | See more information in [Credential Overview](https://github.com/dsccommunity/SqlServerDsc/wiki/CredentialOverview). |
50 | 51 |
|
|
0 commit comments