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/active-directory/authentication/active-directory-passwords-troubleshoot.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ A best practice when you troubleshoot problems with password writeback is to ins
140
140
| 33001| ADUnKnownError| This event indicates that there was an unknown error returned by Active Directory. Check the Azure AD Connect server event log for events from the ADSync source for more information.|
141
141
| 33002| ADUserNotFoundError| This event indicates that the user who is trying to reset or change a password was not found in the on-premises directory. This error can occur when the user has been deleted on-premises but not in the cloud. This error can also occur if there is a problem with sync. Check your sync logs and the last few sync run details for more information.|
142
142
| 33003| ADMutliMatchError| When a password reset or change request originates from the cloud, we use the cloud anchor specified during the setup process of Azure AD Connect to determine how to link that request back to a user in your on-premises environment. This event indicates that we found two users in your on-premises directory with the same cloud anchor attribute. Check your sync logs and the last few sync run details for more information.|
143
-
| 33004| ADPermissionsError| This event indicates that the Active Directory Management Agent (ADMA) service account does not have the appropriate permissions on the account in question to set a new password. Ensure that the ADMA account in the user’s forest has reset and change password permissions on all objects in the forest. For more information on how to set the permissions, see Step 4: Set up the appropriate Active Directory permissions.|
143
+
| 33004| ADPermissionsError| This event indicates that the Active Directory Management Agent (ADMA) service account does not have the appropriate permissions on the account in question to set a new password. Ensure that the ADMA account in the user’s forest has reset and change password permissions on all objects in the forest. For more information on how to set the permissions, see Step 4: Set up the appropriate Active Directory permissions. This error could also occur when the user's attribute AdminCount is set to 1.|
144
144
| 33005| ADUserAccountDisabled| This event indicates that we attempted to reset or change a password for an account that was disabled on-premises. Enable the account and try the operation again.|
145
145
| 33006| ADUserAccountLockedOut| This event indicates that we attempted to reset or change a password for an account that was locked out on-premises. Lockouts can occur when a user has tried a change or reset password operation too many times in a short period. Unlock the account and try the operation again.|
146
146
| 33007| ADUserIncorrectPassword| This event indicates that the user specified an incorrect current password when performing a password change operation. Specify the correct current password and try again.|
Copy file name to clipboardexpand all lines: articles/active-directory/conditional-access/concept-conditional-access-block-legacy-authentication.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,11 @@ Before you can block legacy authentication in your directory, you need to first
30
30
31
31
1. Navigate to the Azure portal > Azure Active Directory > Sign-ins.
32
32
1. Add the Client App column if it is not shown by clicking on Columns > Client App.
33
-
1. Filter by Client App > Other Clients and click Apply.
33
+
1. Filter by Client App > check all the Other Client options presented and click Apply.
34
+
1. Filter by Status > Success and click Apply.
35
+
1. Expand your date range if necessary using the Date filter.
34
36
35
-
Filtering will only show you sign-in attempts that were made by legacy authentication protocols. Clicking on each individual sign-in attempt will show you additional details. The Client App field under the Basic Info tab will indicate which legacy authentication protocol was used.
37
+
Filtering will only show you successful sign-in attempts that were made by the selected legacy authentication protocols. Clicking on each individual sign-in attempt will show you additional details. The Client App column or the Client App field under the Basic Info tab after selecting an individual row of data will indicate which legacy authentication protocol was used.
36
38
These logs will indicate which users are still depending on legacy authentication and which applications are using legacy protocols to make authentication requests. For users that do not appear in these logs and are confirmed to not be using legacy authentication, implement a Conditional Access policy or enable the Baseline policy: block legacy authentication for these users only.
Copy file name to clipboardexpand all lines: articles/ansible/ansible-manage-azure-dynamic-inventories.md
+69-40
Original file line number
Diff line number
Diff line change
@@ -66,11 +66,20 @@ Ansible can be used to pull inventory information from various sources (includin
66
66
67
67
You can [use tags to organize your Azure resources](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-using-tags#azure-cli) by user-defined categories.
68
68
69
+
### Using Ansible version < 2.8
69
70
Enter the following [az resource tag](/cli/azure/resource?view=azure-cli-latest.md#az-resource-tag) command to tag the virtual machine `ansible-inventory-test-vm1` with the key `nginx`:
70
71
71
72
```azurecli-interactive
72
73
az resource tag --tags nginx --id /subscriptions/<YourAzureSubscriptionID>/resourceGroups/ansible-inventory-test-rg/providers/Microsoft.Compute/virtualMachines/ansible-inventory-test-vm1
73
74
```
75
+
76
+
### Using Ansible version >= 2.8
77
+
Enter the following [az resource tag](/cli/azure/resource?view=azure-cli-latest.md#az-resource-tag) command to tag the virtual machine `ansible-inventory-test-vm1` with the key `Ansible=nginx`:
78
+
79
+
```azurecli-interactive
80
+
az resource tag --tags Ansible=nginx --id /subscriptions/<YourAzureSubscriptionID>/resourceGroups/ansible-inventory-test-rg/providers/Microsoft.Compute/virtualMachines/ansible-inventory-test-vm1
81
+
```
82
+
74
83
## Generate a dynamic inventory
75
84
76
85
Once you have your virtual machines defined (and tagged), it's time to generate the dynamic inventory.
@@ -119,10 +128,14 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plugin](
119
128
1. The inventory plugin requires a configuration file. The configuration file must end in `azure_rm` and have an extension of either `yml` or `yaml`. For this tutorial example, save the following playbook as `myazure_rm.yml`:
120
129
121
130
```yml
122
-
plugin: azure_rm
123
-
include_vm_resource_groups:
124
-
- ansible-inventory-test-rg
125
-
auth_source: auto
131
+
plugin: azure_rm
132
+
include_vm_resource_groups:
133
+
- ansible-inventory-test-rg
134
+
auth_source: auto
135
+
136
+
keyed_groups:
137
+
- prefix: tag
138
+
key: tags
126
139
```
127
140
128
141
1. Run the following command to ping VMs in the resource group:
@@ -151,33 +164,49 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plugin](
151
164
```
152
165
153
166
## Enable the VM tag
154
-
Once you've set a tag, you need to "enable" that tag. One way to enable a tag is by exporting the tag to an environment variable `AZURE_TAGS` via the `export` command:
155
167
156
-
```azurecli-interactive
157
-
export AZURE_TAGS=nginx
158
-
```
168
+
### If you're using Ansible < 2.8,
159
169
160
-
- If you're using Ansible < 2.8, run the following command:
170
+
- Once you've set a tag, you need to "enable" that tag. One way to enable a tag is by exporting the tag to an environment variable `AZURE_TAGS` via the `export` command:
Copy file name to clipboardexpand all lines: articles/app-service/containers/app-service-linux-intro.md
+4-13
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,8 @@ description: Learn about Azure App Service on Linux.
4
4
keywords: azure app service, linux, oss
5
5
services: app-service
6
6
documentationcenter: ''
7
-
author: msangapu
8
-
manager: jeconnoc
7
+
author: msangapu-msft
8
+
manager: gwallace
9
9
editor: ''
10
10
11
11
ms.assetid: bc85eff6-bbdf-410a-93dc-0f1222796676
@@ -21,20 +21,11 @@ ms.custom: seodec18
21
21
---
22
22
# Introduction to Azure App Service on Linux
23
23
24
-
[Azure App Service](../overview.md) is a fully managed compute platform that is optimized for hosting websites and web applications. Customers can use App Service on Linux to host web apps natively on Linux for supported application stacks. The [Languages](#languages) section lists the application stacks that are currently supported.
24
+
[Azure App Service](../overview.md) is a fully managed compute platform that is optimized for hosting websites and web applications. Customers can use App Service on Linux to host web apps natively on Linux for supported application stacks.
25
25
26
26
## Languages
27
27
28
-
App Service on Linux supports a number of Built-in images in order to increase developer productivity. If the runtime your application requires is not supported in the built-in images, there are instructions on how to [build your own Docker image](tutorial-custom-docker-image.md) to deploy to Web App for Containers.
App Service on Linux supports a number of Built-in images in order to increase developer productivity. Languages include: Node.js, Java (JRE 8 & JRE 11), PHP, Python, .NET Core and Ruby. Run [`az webapp list-runtimes --linux`](https://docs.microsoft.com/cli/azure/webapp?view=azure-cli-latest#az-webapp-list-runtimes) to view the latest languages and supported versions. If the runtime your application requires is not supported in the built-in images, there are instructions on how to [build your own Docker image](tutorial-custom-docker-image.md) to deploy to Web App for Containers.
Copy file name to clipboardexpand all lines: articles/app-service/overview-local-cache.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ You enable Local Cache on a per-web-app basis by using this app setting:
90
90
```
91
91
92
92
## Change the size setting in Local Cache
93
-
By default, the local cache size is **300 MB**. This includes the /site and /siteextensions folders that are copied from the content store, as well as any locally created logs and data folders. To increase this limit, use the app setting `WEBSITE_LOCAL_CACHE_SIZEINMB`. You can increase the size up to **2 GB** (2000 MB) per app.
93
+
By default, the local cache size is **1 GB**. This includes the /site and /siteextensions folders that are copied from the content store, as well as any locally created logs and data folders. To increase this limit, use the app setting `WEBSITE_LOCAL_CACHE_SIZEINMB`. You can increase the size up to **2 GB** (2000 MB) per app.
94
94
95
95
## Best practices for using App Service Local Cache
96
96
We recommend that you use Local Cache in conjunction with the [Staging Environments](../app-service/deploy-staging-slots.md) feature.
@@ -102,6 +102,7 @@ We recommend that you use Local Cache in conjunction with the [Staging Environme
102
102
* Sticky settings include name and sticky to a slot. So when the Staging slot gets swapped into Production, it inherits the Local Cache app settings. The newly swapped Production slot will run against the local cache after a few minutes and will be warmed up as part of slot warmup after swap. So when the slot swap is complete, your Production slot is running against the local cache.
103
103
104
104
## Frequently asked questions (FAQ)
105
+
105
106
### How can I tell if Local Cache applies to my app?
106
107
If your app needs a high-performance, reliable content store, does not use the content store to write critical data at runtime, and is less than 2 GB in total size, then the answer is "yes"! To get the total size of your /site and /siteextensions folders, you can use the site extension "Azure Web Apps Disk Usage."
0 commit comments