Intune 2610 Push for Scripts: Check Delivery Before Success
Faster delivery does not prove that a script ran or that the device reached the intended state.
Read articleBrowse practical guides, code and worked examples. Choose a topic or use the search to find a specific task.
Find older articles by year · Setup references
Faster delivery does not prove that a script ran or that the device reached the intended state.
Read articleSee what the Ignite announcements change for local agents, endpoint patching and identity management.
Read articleThe blueprint-creation switch is not a data-access permission; review both boundaries before opening agent development.
Read articleBuild a small spoken support pilot with a Learn toolbox, clear instructions and tests for clarifying questions.
Read articleApprove downloads with a reason, account for Google's redirect in a block rule and check browser restrictions on a Windows client.
Read articleUpdate a policy, revoke access and delete its source, then test what the agent can still retrieve or reuse. Follow the data through the index, cache and conversation.
Read articleFollow a browser task from agent creation to its trace, including workspace setup and a narrower retry after timeouts.
Read articlePrepare a scheduled agent with a fixed identity and time zone. Use a business-job key and delivery state to stop duplicate reports and ambiguous retries.
Read articlePut a budget check before each model call, reserve capacity for requests already running and investigate retries before comparing model prices.
Read articleSee how AgentDome attributes AI usage, proposes optimizations and connects targeted changes with follow-up reporting.
Read articleInspect what your agent receives before its first tool call. Add deferred tool discovery, then test whether it still finds the right read-only operation.
Read articleRun the credential-free Harness² example, inspect the changed calculation and use a separate evaluation gate before adopting an agent's proposed improvements.
Read article