Skip to content

Commit 1a92764

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 0cb3ca2 + b2fb32a commit 1a92764

36 files changed

+171
-107
lines changed

articles/active-directory/manage-apps/user-provisioning.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
1919
---
2020
# Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory
2121

22-
Azure Active Directory (Azure AD) lets you automate the creation, maintenance, and removal of user identities in cloud ([SaaS](https://azure.microsoft.com/overview/what-is-saas/)) applications such as Dropbox, Salesforce, ServiceNow, and more. This is known as automated user provisioning for SaaS apps.
22+
Azure Active Directory (Azure AD) lets you automate the creation, maintenance, and removal of user identities in cloud SaaS applications such as [Dropbox](https://docs.microsoft.com/azure/active-directory/saas-apps/dropboxforbusiness-provisioning-tutorial), [Salesforce](https://docs.microsoft.com/azure/active-directory/saas-apps/salesforce-provisioning-tutorial), [ServiceNow](https://docs.microsoft.com/azure/active-directory/saas-apps/servicenow-provisioning-tutorial), and more. This is known as automated user provisioning for SaaS apps.
2323

2424
> [!VIDEO https://www.youtube.com/embed/_ZjARPpI6NI]
2525
@@ -85,11 +85,7 @@ Use the Azure Active Directory portal to configure the Azure AD provisioning ser
8585

8686
1. Open the **[Azure Active Directory portal](https://aad.portal.azure.com)**.
8787
1. Select **Enterprise applications** from the left pane. A list of all configured apps is show.
88-
1. Choose **+ New application** to add an application. Add either of the following depending on your scenario:
89-
90-
- The **Add your own app** option supports custom-developed SCIM integrations.
91-
- All applications in the **Add from the gallery** > **Featured applications** section support automatic provisioning. See the [list of application tutorials for user provisioning](../saas-apps/tutorial-list.md) for additional ones.
92-
88+
1. Choose **+ New application** to add an application.
9389
1. Provide any details and select **Add**. The new app is added to the list of enterprise applications and opens to its application management screen.
9490
1. Select **Provisioning** to manage user account provisioning settings for the app.
9591

articles/active-directory/reports-monitoring/concept-provisioning-logs.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,9 @@ The **summary** tab provides an overview of what happened and identifiers for th
204204

205205
## Error Codes
206206

207-
|ErrorCode|Description|
207+
Use the table below to better understand how to resolve errors you may find in the provisioning logs. For any error codes that are missing, provide feedback using the link at the bottom of this page.
208+
209+
|Error Code|Description|
208210
|---|---|
209211
|Conflict, EntryConflict|Correct the conflicting attribute values in either Azure AD or the application, or review your matching attribute configuration if the conflicting user account was supposed to be matched and taken over. Review the following [documentation](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes) for more information on configuring matching attributes.|
210212
|TooManyRequests|The target app rejected this attempt to update the user because it is overloaded and receiving too many requests. There is nothing to do. This attempt will automatically be retired. Microsoft has also been notified of this issue.|

articles/active-directory/saas-apps/tutorial-list.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ To help integrate your cloud-enabled [software as a service (SaaS)](https://azur
2626

2727
For a list of all SaaS apps that have been pre-integrated into Azure AD, see the [Active Directory Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/category/azure-active-directory-apps).
2828

29+
Use the [application network portal](https://docs.microsoft.com/azure/active-directory/develop/howto-app-gallery-listing) to request a [SCIM](https://docs.microsoft.com/azure/active-directory/manage-apps/use-scim-to-provision-users-and-groups) enabled application to be added to the gallery for automatic provisioning or a SAML / OIDC enabled application to be added to the gallery for SSO.
30+
2931
## Quick links
3032

3133
| Logo | Application tutorial for single sign-on | Application tutorial for user provisioning |
@@ -112,4 +114,4 @@ To find more tutorials, use the table of contents on the left.
112114

113115
## Next steps
114116

115-
To learn more about application management, see [What is application management](../manage-apps/what-is-application-management.md).
117+
To learn more about application management, see [What is application management](../manage-apps/what-is-application-management.md).

articles/azure-functions/functions-bindings-service-bus.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.ServiceBus
2828

2929
## Packages - Functions 2.x
3030

31-
The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.Extensions.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ServiceBus) NuGet package, version 3.x. Source code for the package is in the [azure-webjobs-sdk](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Extensions.ServiceBus/) GitHub repository.
31+
The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.Extensions.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ServiceBus) NuGet package, version 3.x. Source code for the package is in the [azure-functions-servicebus-extension](https://github.com/Azure/azure-functions-servicebus-extension) GitHub repository.
3232

3333
> [!NOTE]
3434
> Version 2.x does not create the topic or subscription configured in the `ServiceBusTrigger` instance. Version 2.x is based on [Microsoft.Azure.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.ServiceBus) and does not handle queue management.

articles/azure-monitor/log-query/examples.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,6 @@ let EndTime = now()-4d;
171171
Perf
172172
| where CounterName == "% Processor Time"
173173
| where TimeGenerated > StartTime and TimeGenerated < EndTime
174-
and TimeGenerated < EndTime
175174
| project TimeGenerated, Computer, cpu=CounterValue
176175
| join kind= inner (
177176
Perf

articles/backup/backup-azure-arm-userestapi-createorupdatepolicy.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.assetid: 5ffc4115-0ae5-4b85-a18c-8a942f6d4870
1313
---
1414
# Create Azure Recovery Services backup policies using REST API
1515

16-
The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
16+
The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
1717

1818
## Backup policy essentials
1919

@@ -46,10 +46,10 @@ For example, to create a policy for Azure VM backup, following are the component
4646

4747
|Name |Required |Type |Description |
4848
|---------|---------|---------|---------|
49-
|properties | True | ProtectionPolicy:[AzureIaaSVMProtectionPolicy](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate#azureiaasvmprotectionpolicy) | ProtectionPolicyResource properties |
49+
|properties | True | ProtectionPolicy:[AzureIaaSVMProtectionPolicy](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate#azureiaasvmprotectionpolicy) | ProtectionPolicyResource properties |
5050
|tags | | Object | Resource tags |
5151

52-
For the complete list of definitions in the request body, refer to the [backup policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate).
52+
For the complete list of definitions in the request body, refer to the [backup policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate).
5353

5454
### Example request body
5555

@@ -150,11 +150,11 @@ The policy says:
150150

151151
The backup policy creation/update is a [asynchronous operation](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-async-operations). It means this operation creates another operation that needs to be tracked separately.
152152

153-
It returns two responses: 202 (Accepted) when another operation is created and then 200 (OK) when that operation completes.
153+
It returns two responses: 202 (Accepted) when another operation is created, and then 200 (OK) when that operation completes.
154154

155155
|Name |Type |Description |
156156
|---------|---------|---------|
157-
|200 OK | [Protection PolicyResource](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate#protectionpolicyresource) | OK |
157+
|200 OK | [Protection PolicyResource](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate#protectionpolicyresource) | OK |
158158
|202 Accepted | | Accepted |
159159

160160
### Example responses
@@ -279,7 +279,7 @@ If a policy is already being used to protect an item, any update in the policy w
279279

280280
[Enable protection for an unprotected Azure VM](backup-azure-arm-userestapi-backupazurevms.md).
281281

282-
For more information on the Azure Backup REST APIs, refer to the following documents:
282+
For more information on the Azure Backup REST APIs, see the following documents:
283283

284284
- [Azure Recovery Services provider REST API](/rest/api/recoveryservices/)
285-
- [Get started with Azure REST API](/rest/api/azure/)
285+
- [Get started with Azure REST API](/rest/api/azure/)

articles/backup/backup-sql-server-azure-troubleshoot.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,6 @@ To configure protection for a SQL Server database on a virtual machine, you must
2828
|---|---|---|---|
2929
| Warning | Current settings for this database don't support certain backup types present in the associated policy. | <li>Only a full database backup operation can be performed on the master database. Neither differential backup nor transaction log backup is possible. </li> <li>Any database in the simple recovery model does not allow for the backup of transaction logs.</li> | Modify the database settings such that all the backup types in the policy are supported. Or, change the current policy to include only the supported backup types. Otherwise, the unsupported backup types will be skipped during scheduled backup or the backup job will fail for ad hoc backup.
3030

31-
3231
### UserErrorSQLPODoesNotSupportBackupType
3332

3433
| Error message | Possible causes | Recommended action |
@@ -78,7 +77,7 @@ To configure protection for a SQL Server database on a virtual machine, you must
7877
|---|---|---|
7978
| Restore failed as the database could not be brought offline. | While you're doing a restore, the target database needs to be brought offline. Azure Backup can't bring this data offline. | Use the additional details on the Azure portal error menu to narrow down the root causes. For more information, see the [SQL Server documentation](https://docs.microsoft.com/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms). |
8079

81-
### UserErrorCannotFindServerCertificateWithThumbprint
80+
### UserErrorCannotFindServerCertificateWithThumbprint
8281

8382
| Error message | Possible causes | Recommended action |
8483
|---|---|---|
@@ -90,7 +89,6 @@ To configure protection for a SQL Server database on a virtual machine, you must
9089
|---|---|---|
9190
| The log backup used for recovery contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time as per the SQL guidelines. | When a database is in bulk-logged recovery mode, the data between a bulk-logged transaction and the next log transaction can't be recovered. | Choose a different point in time for recovery. [Learn more](https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms186229(v=sql.105)).
9291

93-
9492
### FabricSvcBackupPreferenceCheckFailedUserError
9593

9694
| Error message | Possible causes | Recommended action |
@@ -125,8 +123,7 @@ Operation is blocked as you have reached the limit on number of operations permi
125123

126124
| Error message | Possible causes | Recommended action |
127125
|---|---|---|
128-
Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours. | When you have reached the maximum permissible limit for an operation in a span of 24 hours, this error comes. This error usually comes in case of at-scale operations such as modify policy or auto-protection. Unlike in the case of CloudDosAbsoluteLimitReached, there is not much you can do to resolve this state, in fact, Azure Backup service will retry the operations internally for all the items in question.<br> For example: If you have a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.| Azure Backup service will automatically retry this operation after 24 hours.
129-
126+
Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours. | When you have reached the maximum permissible limit for an operation in a span of 24 hours, this error comes. This error usually comes when there are at-scale operations such as modify policy or auto-protection. Unlike in the case of CloudDosAbsoluteLimitReached, there is not much you can do to resolve this state, in fact, Azure Backup service will retry the operations internally for all the items in question.<br> For example: If you have a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.| Azure Backup service will automatically retry this operation after 24 hours.
130127

131128
## Re-registration failures
132129

@@ -145,14 +142,14 @@ Check for one or more of the following symptoms before you trigger the re-regist
145142

146143
These symptoms may arise for one or more of the following reasons:
147144

148-
* An extension was deleted or uninstalled from the portal.
145+
* An extension was deleted or uninstalled from the portal.
149146
* An extension was uninstalled from **Control Panel** on the VM under **Uninstall or Change a Program**.
150147
* The VM was restored back in time through in-place disk restore.
151148
* The VM was shut down for an extended period, so the extension configuration on it expired.
152149
* The VM was deleted, and another VM was created with the same name and in the same resource group as the deleted VM.
153150
* One of the availability group nodes didn't receive the complete backup configuration. This can happen when the availability group is registered to the vault or when a new node is added.
154151

155-
In the preceding scenarios, we recommend that you trigger a re-register operation on the VM. For now, this option is available only through PowerShell.
152+
In the preceding scenarios, we recommend that you trigger a re-register operation on the VM. See [here](https://docs.microsoft.com/azure/backup/backup-azure-sql-automation#enable-backup) for instructions on how to perform this task in PowerShell.
156153

157154
## Size limit for files
158155

@@ -183,6 +180,7 @@ If the string size of the content exceeds 20,000 bytes, the database files are s
183180
You can override the target restore file path during the restore operation by placing a JSON file that contains the mapping of the database file to the target restore path. Create a `database_name.json` file and place it in the location *C:\Program Files\Azure Workload Backup\bin\plugins\SQL*.
184181
185182
The content of the file should be in this format:
183+
186184
```json
187185
[
188186
  {
@@ -223,7 +221,6 @@ SELECT mf.name AS LogicalName FROM sys.master_files mf
223221
              WHERE db.name = N'<Database Name>'"
224222
```
225223

226-
227224
This file should be placed before you trigger the restore operation.
228225

229226
## Next steps

0 commit comments

Comments
 (0)